How do I retry a failed task without duplicating work?

Inspect partial outputs before retrying. A failed response or interrupted run can still have written files or completed external actions, so repeating the whole task may duplicate them.

Before you begin

Task status describes execution, not whether the result is factually correct or ready to publish. Keep the original input and inspect the actual output file. Task details, results and execution events provide different evidence; use them together when deciding whether to accept, revise or retry work.

Steps

1. Read the last successful event.
2. Check the work folder and any external action already taken.
3. Keep useful partial files.
4. Use the available retry or run-again action with clear scope.

Example

If a task created three of five summaries, ask it to finish the two missing files and preserve the existing ones, rather than regenerating all five.

Check the result

Compare filenames, timestamps and content after the retry. Check for duplicates and unintended overwrites.

Limits and troubleshooting

OfficeCubs cannot infer every external side effect from a missing response. Review consequential tool actions separately.