You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Gotify and Ntfy settings fail to persist serverThreshold preference + Teams notification unhandled rejection #5175
Navigate to the Settings > Notifications page in the dashboard.
Select Gotify (or Ntfy) as the notification provider.
Toggle the Server Threshold switch to ON (enabled).
Click Save to create or update the notification setting.
Refresh the page or click back into the Gotify/Ntfy notification setting.
Observe that the Server Threshold switch has reset to OFF (disabled) and the preference was not saved to the database.
For the Teams error boundary issue:
Configure a Teams notification with an invalid webhook URL (or simulate a network failure).
Trigger a server threshold alert condition.
Observe that the sendTeamsNotification function throws an error, but because it sits outside the try/catch loop in packages/server/src/utils/notifications/server-threshold.ts, the error escapes as an unhandled rejection.
Observe that any remaining notification providers configured for that threshold alert are never processed.
Current vs. Expected behavior
Gotify/Ntfy Server Threshold Persistence:
Current Behavior: The serverThreshold UI preference for Gotify and Ntfy is silently stripped during backend validation (apiCreateGotify/apiCreateNtfy schemas) and is omitted from the database inserts/updates in the service layer.
Expected Behavior: The preference should successfully persist in the database and hydrate correctly in the UI upon refresh, matching the behavior of the other 9 notification providers.
Teams Error Boundary:
Current Behavior: If the sendTeamsNotification dispatcher fails in server-threshold.ts, it causes an unhandled rejection that breaks out of the notification processing loop entirely.
Expected Behavior: The Teams notification dispatcher should be wrapped inside the loop's try/catch block (like all other dispatchers in the codebase) so that a failure gracefully logs the error and allows the loop to continue sending notifications to other configured providers.
Which area(s) are affected? (Select all that apply)
Local Development
Are you deploying the applications where Dokploy is installed or on a remote server?
Same server where Dokploy is installed
Additional context
Proposed Solution
Add serverThreshold: true to the Zod validation schemas and service layers for Gotify and Ntfy, matching the other providers. Add the field to the UI form.reset and mutateAsync payloads.
Move the if (teams) block inside the try/catch in server-threshold.ts.
Activity
linear-code commentedon Aug 24, 2026
DOK-689