Writing an error-handling note for a workflow

For each fragile step, describe the visible failure, the first safe check, when to retry, and when to stop. Include where partial output lands so it is not mistaken for a completed result.

Make retries idempotent when possible: rerunning should not create duplicate messages or records. State who receives an unresolved failure and how to protect secrets in logs or screenshots. Test the note against one realistic failure before calling it done.

Which step has the least clear recovery path?