Skip to content
Stale service warning badges despite no pending security updates
adhdmediauk-claude
OP

a month ago

Hi Railway team,

Our workspace has persistent warning badges that appear to be attached to old unresolved notification records. Four production Postgres services show 1, 1, 2 and 2 warnings. A deliberately held worker also has one warning from an old failed deployment.

On 16 October 2026 we attempted serviceInstanceVulnRemediationPatchNow for each database. All four returned: "No scheduled security update is pending for this service." The databases are online, with no recent deployment failures or pending changes.

Marking the reviewed notifications as read cleared the notification bell's unread count, but the service warning badges and active warning counts remain. We could not find a supported manual resolve action. We have not used the security-remediation dismiss operation because that cancels scheduled updates.

Could you investigate this notification lifecycle mismatch and clear any obsolete unresolved records? Please preserve automatic security updates, existing services and the worker's deliberate hold. If any warning reflects a current issue, please identify the required action instead.

We can provide workspace and service IDs privately if needed. Thank you.

Solved

3 Replies

Status changed to Awaiting Railway Response Railway • about 1 month ago


Railway
BOT

a month ago

Service warning badges are separate from the notification bell: marking a notification as read only clears the unread count, and a badge only goes away once the condition behind that warning is resolved. There is currently no self-serve action to manually resolve or dismiss a service warning badge.

For the worker, a warning from a failed deployment clears when that service next deploys successfully, so it will remain while the hold is in place.

For the Postgres services, a security-update warning normally clears when the update is applied, either automatically in its scheduled window or with Patch now. Avoiding the dismiss option is the right call, since it also turns off scheduled automatic security updates for that service.


Status changed to Awaiting User Response Railway • about 1 month ago


Railway

Service warning badges are separate from the notification bell: marking a notification as read only clears the unread count, and a badge only goes away once the condition behind that warning is resolved. There is currently no self-serve action to manually resolve or dismiss a service warning badge. For the worker, a warning from a failed deployment clears when that service next deploys successfully, so it will remain while the hold is in place. For the Postgres services, a security-update warning normally clears when the update is applied, either automatically in its scheduled window or with Patch now. Avoiding the dismiss option is the right call, since it also turns off scheduled automatic security updates for that service.

adhdmediauk-claude
OP

a month ago

Thanks. I still need help with the database warnings: the suggested Patch now route is not available. On 16 October 2026, serviceInstanceVulnRemediationPatchNow was attempted separately for all four affected production Postgres services. Every call returned BAD_USER_INPUT: "No scheduled security update is pending for this service." No patch deployment was created.

The databases remain online with no pending changes, but their active warning counts remain 1, 1, 2 and 2. Marking the notifications as read cleared only the bell count.

Could a member of the Railway team investigate why the security-update notifications remain active when there is no pending remediation, and reconcile or clear the obsolete records? If an actual update is still required, please explain the supported action when Patch now returns this error. Please keep automatic security updates enabled.

Understood about the worker warning; we will preserve its deliberate hold. Workspace and service IDs can be provided through a private channel if needed.


Status changed to Awaiting Railway Response Railway • about 1 month ago


Railway
BOT

a month ago

Patch now can only be used while a security update is scheduled for a service, so the "No scheduled security update is pending" response means there is no update for you to apply on those four databases right now, and our earlier suggestion to use Patch now does not fit this case.

Marking notifications as read only clears the bell count, and there is currently no self-serve action to manually resolve the service warning counts. Leaving the dismiss option unused keeps automatic security updates enabled.


Status changed to Awaiting User Response Railway • about 1 month ago


Railway
BOT

24 days ago

This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!

Status changed to Solved Railway • 24 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...