Retry a failed run or revise the brief?

Retry when the original goal and instructions remain correct and the failure was environmental. Revise when the task exposed ambiguity, missing inputs or an unsuitable output requirement.

Compare the practical differences

Decision	Retry	Revised task
Best fit	Temporary interruption after checking partial work	Incorrect assumptions or unclear requirements
Useful property	Can reuse a valid task goal	Addresses the cause in the brief
What to check	May repeat writes or external actions	Needs explicit treatment of existing output

A concrete choice

A provider connection failure may justify a retry after recovery. A report using the wrong definition of revenue needs a corrected brief and source definition.

Verify the choice

Inspect partial files before either path and confirm the new attempt does not overwrite an accepted artifact unintentionally.

Write the reason for your choice into the task brief or setup notes. Then run a small representative task and compare the actual result with the requirement that drove the decision. Keep any unmet requirement visible rather than declaring the whole workflow ready from a single successful step.

Continue with the setup

The related desktop guide explains the relevant controls and limits. Use the current application state when applying this comparison; the presence of an option in a document does not mean every dependency on your computer is ready.