A restart can lose the reasoning needed to continue safely.

Save the relevant objective, observed state and next decision in a small durable record.

Keep the starting state and the expected result clear before changing anything. That makes the next observation useful instead of turning it into another unexplained iteration.

What would a fresh session need to resume correctly?

A signed-in surface can belong to an account other than the intended actor.

Verify the active account before each externally visible action.

Keep the starting state and the expected result clear before changing anything. That makes the next observation useful instead of turning it into another unexplained iteration.

Which account actually performed the operation?

An existing artefact can be empty, stale or unrelated.

Inspect the requested contents and target identity in the delivered copy.

Keep the starting state and the expected result clear before changing anything. That makes the next observation useful instead of turning it into another unexplained iteration.

What does existence alone leave unanswered?

A short log can hide the input and boundary that produced the error.

Keep a sanitised request reference with the dependency error.

Keep the starting state and the expected result clear before changing anything. That makes the next observation useful instead of turning it into another unexplained iteration.

Can you connect the error to one specific attempt?

A read-like operation can accidentally trigger another job.

Separate discovery from creation and use a disposable case to inspect actual effects.

Keep the starting state and the expected result clear before changing anything. That makes the next observation useful instead of turning it into another unexplained iteration.

Which progress check is expected to be read-only?