The emergency path works, but cleanup logic later tears down the wrong environment state. The functional path still exists, but one hidden dependency still assumes the old boundary between shared and isolated resources. A hidden dependency still assumes the old shared-service boundary even though the visible workflow stayed intact. The visible workflow still functions, but one dependency continues to assume the previous shared ownership contract.
The emergency path works, but cleanup logic later tears down the wrong environment state. The functional path still exists, but one hidden dependency still assumes the old boundary between shared and isolated resources. A hidden dependency still assumes the old shared-service boundary even though the visible workflow stayed intact. The visible workflow still functions, but one dependency continues to assume the previous shared ownership contract.
Choose the smallest safe recovery action first, then record the prevention work that reduces repeat incidents.
No. Keep commands, logs, file names, APIs, and product names unchanged, then explain the reasoning in the selected UI language.
State the root cause, the evidence that supports it, and the safest recovery direction.
The source scenario is treated as an incident artifact. Guidance, checklist, hints, and explanations can be localized around it.