Check deployment status
Verify readiness and configuration acceptance on the intended runtime.
Before you start
Section titled “Before you start”Identify the environment and data-plane replicas that serve the affected endpoint. Use an operator identity with diagnostic access.
Procedure
Section titled “Procedure”-
Inspect deployment status and dependency diagnostics for the control plane and data planes.
-
Confirm readiness, recent managed Fleet heartbeats where applicable, and the accepted projection on each serving replica.
-
Check whether the desired configuration has been acknowledged. One updated replica is not proof that the whole fleet converged.
-
Run a harmless governed request through the deployed route and locate its audit record.
Verify the result
Section titled “Verify the result”Record the time, scope, readiness result, projection identity, and governed-call outcome. Redact internal diagnostic values before sharing.
If it does not work
Section titled “If it does not work”An old or missing projection can block readiness even while the process is running. Investigate delivery and validation before restarting a healthy process.
Read the related concept or consult the Admin API for exact request fields.
Implementation reference
Section titled “Implementation reference”Amelfi documentation · Space Grotesk / Geist Mono