SYSE.41:4.5 - Reconcile partial failure before repeating

After timeout or interruption, query what took effect. Compare actual state with the intended result and choose a qualified continuation, removal or return. Repeat only steps whose effects and replay behavior are known.

Keep an unqualified candidate out of ordinary reliance where the architecture and authority permit that separation. Preserve the working prior service rather than damaging it during an uncertain repair. If the old service is no longer available, state that constraint instead of assuming a rollback path.

Use SYSE.34 before returning binaries across a changed data boundary. If effects or readback remain unknown, stop the operation that could create duplicate resources, repeat external effects or corrupt stored data, and request the exact missing observation or specialist result. A “failed deployment” label does not establish that no state changed.