Service status
What this deployment observed about itself and its work queue. There is no incident, support or feature-flag operation in this build.
Note: Only this deployment, and only what it could read
Development and production are separate deployments with separate databases and there is no channel between them, so nothing here reports the other environment. The service rows for both environments, side by side, are on the Overview screen.
Loading the measured state…
What this area does not have
The concept’s Operations area is five screens. None of the operations behind the five below is registered in this deployment, so there is no screen for them and nothing here simulates one. Every id is the name the frozen contract uses — grep one and you find the declaration and no handler, which is the difference between a missing implementation and a typo on this page.
Jobs and queues — a job list, a job's steps, retry and cancel (OPS-001)staffJobsList · staffJobGet · staffJobRetry · staffJobCancel
Notification delivery operations (OPS-002) — read on the Communications screen instead, which reports the counts this deployment measuredstaffCommDeliveriesList · staffCommDeliveryGet · staffCommDeliveryRetryCommit
Incidents — declaring one and its timeline (OPS-003). The customer-facing status page the concept drives from it has no write operation in the contract at all, under any namestaffIncidentsList · staffIncidentCreate · staffIncidentUpdate
Feature flags and rollout (OPS-004)staffFlagsList · staffFlagPreview · staffFlagPublish · staffFlagRollback
Working a support case — replying to one, noting it internally, assigning and closing it, and the support session a staff operator opens against an account (OPS-005). The queue itself is built, at /support/casesstaffSupportCaseUpdate · staffSupportCaseReply · staffSupportSessionPreview · staffSupportSessionStart · staffSupportSessionEnd · staffSupportNoteCreate