Short answer: you’re not imagining it — the dedicated “Incidents” page was removed from the Prefect Cloud UI recently, but the underlying Incidents APIs and automation action still exist. What I can confirm right now - Incidents were introduced as a Cloud beta feature; see the original announcement: Incidents changelog and blog post. - The SDK still exposes the

DeclareIncident

automation action in Prefect 3.x:

from prefect.automations import DeclareIncident

- I couldn’t find a public deprecation/sunset note specifically about removing the Incidents UI navigation. The latest OSS release notes don’t mention Cloud UI changes either. What this means for you - Existing automations that declare incidents should continue to work. - If you were relying on the UI to browse incidents, that view is no longer in the main navigation. Depending on your org, a direct URL may or may not still resolve; if you have a bookmark, try it. If it 404s, the page has been fully disabled for your workspace. Questions to help me escalate/verify for your account - Are you on Prefect Cloud, and which region (US/EU) and workspace are affected? - Do you still need a dedicated UI for incidents (e.g., reporting/compliance), or would alternatives like Automations + Notifications + Events feed filters cover your use case? Workarounds/alternatives right now - Use Automations to declare and notify on incidents (the action still works), and rely on Notifications and the Events feed for visibility. - If you’re programmatically consuming incidents, continue using the API endpoint you mentioned; it’s still live. If you share your org/workspace details (DM is fine), I’ll check internally on the status for your tenant and whether there’s a replacement UI or timeline we can share. In the meantime, if you want, I can help recreate your incident visibility via an automation + notification pattern.