Get revision status
Reports the deploy state of one revision, and its state and session slots in each region. To wait for a rollout, poll this route for the revision that your write created. Stop when state is ready, stopped or failed. Also stop on superseded, which means that a later write replaced the revision. degraded and unknown can last, so set a timeout.
Reactor computes the status on each read, with the same lag as the environment status. An unreadable region does not fail the read. The read answers 200, with observed_at and summary null for that region. The response has Cache-Control: no-store. Requires the account_admin or developer role in the owning account.
Authorizations
Path Parameters
Response
The revision's status.