The short answer
Then check output paths, tools and account allowances. Preserve the exact error instead of creating duplicate concurrent tasks.
Try it in three steps
- Record time, status and the last message.
- Inspect the results view for artifacts and skipped items.
- Use official troubleshooting guidance and escalate when needed.
A practice prompt
Before you start
Diagnose by stage rather than retrying blindly.
Practice material (fictional)
State: awaiting confirmation. Last message: approve writing draft.txt. No output exists yet.Replace placeholders in the prompt with this material, or append the material if there are no placeholders. Reading time excludes doing the exercise.
Diagnose the stalled step and report the exact error and existing artifacts without retrying, duplicating or broadening access.What to look for (not a recorded test result)
This is awaiting write approval, not necessarily a crash. Review the action before deciding; do not duplicate the task. Other states require their actual errors.
If it goes wrong
Check uncertain results before retries, especially when an external submission may already have occurred.
Check your result
You can report the actual state and smallest next action without labeling a stall complete.
References and scope
The links below support the concepts or product navigation. The steps and exercises are our teaching suggestions, not official certification or measured customer outcomes. Product interfaces and availability may change. References checked on 2026-10-17.