Separate deployment success from a rate-limited final audit

A release workflow can fail after every Railway deployment succeeds when a final read-only audit is rate-limited. Do not infer rollback or application failure from the workflow’s terminal status alone. Reconcile each service’s latest deployment ID, immutable release marker, runtime status, and intended scheduler state from Railway after the cooldown; then rerun only the audit if the workflow supports it, or record the audit gap explicitly. This does not excuse a failed build, migration, health check, or mismatched release marker.

Applies when: a deployment workflow fails during post-deploy verification after successful service rollouts. Keywords: Railway deployment rate limit final audit immutable release verification