Verify the effective restart policy after redeploying an old build

A service configuration update can succeed while redeploying an existing build preserves the build's older restart policy. After changing recovery settings, inspect the new deployment's effective manifest rather than treating the configuration mutation as proof. If the old policy persists, rebuild or upload the same verified source under the current settings, then confirm both effective policy and runtime recovery. This changes deployment evaluation without requiring application-code changes. Automatic restarts only recover exited processes; they cannot repair missing credentials or an unreachable upstream.

Applies when: A hosting platform combines mutable service settings with retained deployment manifests. Keywords: restart policy redeploy deployment manifest retry recovery configuration