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
On Railway status page (https://status.railway.app/) they call it "notice" instead of "incident", since not everything is an incident anyway. Maybe we should convert our wording into that.
But.. we still need a database schema for storing those notices. It should include this data (as minimum):
Title -> the title of the notice
Timestamp -> Event timestamp
Status -> must be one of "investigating" | "identified" | "monitoring" | "resolved" | "scheduled". If the timestamp is in the future, the status must only be "scheduled"
On Railway status page (https://status.railway.app/) they call it "notice" instead of "incident", since not everything is an incident anyway. Maybe we should convert our wording into that.
But.. we still need a database schema for storing those notices. It should include this data (as minimum):
timestamp
is in the future, the status must only be "scheduled"Some examples on how we would display this on the frontend:
Incident detail:
The text was updated successfully, but these errors were encountered: