From 1c0dbbcfd6525626173046a193ce313510b90cac Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=D0=92=D0=BE=D0=BB=D0=BA=D0=BE=D0=B2=20=D0=94=D0=BC=D0=B8?=
 =?UTF-8?q?=D1=82=D1=80=D0=B8=D0=B9=20=D0=A1=D0=B5=D1=80=D0=B3=D0=B5=D0=B5?=
 =?UTF-8?q?=D0=B2=D0=B8=D1=87?= <dsvolkov@gid.ru>
Date: Tue, 10 Mar 2026 23:10:37 +0500
Subject: [PATCH] fix: invalidate notification.one query cache on update

When editing a notification, only the notification.all query cache was
invalidated. The notification.one query retained stale data, causing
the edit form to display previous values on subsequent edits.
---
 .../dashboard/settings/notifications/handle-notifications.tsx  | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/apps/dokploy/components/dashboard/settings/notifications/handle-notifications.tsx b/apps/dokploy/components/dashboard/settings/notifications/handle-notifications.tsx
index 6ef1e15dbd..c4e5495730 100644
--- a/apps/dokploy/components/dashboard/settings/notifications/handle-notifications.tsx
+++ b/apps/dokploy/components/dashboard/settings/notifications/handle-notifications.tsx
@@ -737,6 +737,9 @@ export const HandleNotifications = ({ notificationId }: Props) => {
 					});
 					setVisible(false);
 					await utils.notification.all.invalidate();
+					if (notificationId) {
+						await utils.notification.one.invalidate({ notificationId });
+					}
 				})
 				.catch(() => {
 					toast.error(