a month ago
Description:
I'm experiencing an issue where a resolved deployment crash notification continues to appear in the Railway dashboard interface, even though it has been marked as read and resolved.
What I've tried:
Marked all old notifications as read
Refreshed the page multiple times
Confirmed the current deployment is healthy (1 replica running, 0 crashed, application processing requests normally)
Verified via the notification data that the notification status is "RESOLVED" and "readAt" is populated
The issue: An old notification (from several days ago) still displays in the notifications section despite:
Being historical (several days old)
Having status marked as RESOLVED
The service being online and healthy
Notification details:
Event Type: Deployment.crashed
Severity: CRITICAL
Status: RESOLVED
The notification payload confirms resolution but it's still visible in the UI
This appears to be a UI synchronization issue where resolved notifications remain visible even though their backend status is correctly updated.
1 Replies
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
Try a hard refresh (Ctrl+Shift+R / Cmd+Shift+R) or logging out and back in to clear the stale notification state. If it persists after that, let us know.
Status changed to Awaiting User Response Railway • about 1 month ago
a month 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 • 28 days ago