How to Check Subtask Status and Use Its Results?
Distinguish between queued, working, completed, failed, and canceled statuses, then integrate by the main task.
Check Status Before Conclusions
The subtask interface can display queued, working, wrapping up, completed, failed, canceled, or timed out statuses when the feature is available. Queued does not mean verification has started, and completed does not automatically indicate confirmed findings; you still need to review result explanations and evidence.
If there is no summary, you can wait for activity records to load; do not infer task success from a blank detail page.
How the Main Task Uses Results
The main task needs to receive and integrate subtask outputs to form the final answer. You can request it to specify which conclusions come from which checks and how contradictions are resolved.
If one subtask completes while another times out, you can retain the evidence from the completed part and clearly state that the remaining conclusions are still pending review. Do not hide failure statuses just to present a tidy final answer; let the main task explain gaps and conditions needed for the next continuation.
- Check each subtask's goal and actual status.
- Read successful results and reasons for failure or cancellation.
- Verify key conclusions against corresponding evidence.
- Only redo unfinished parts to avoid rerunning everything.
After Cancellation and Failure
When needing to stop an individual subtask, use the cancel operation actually provided in the details and confirm the status change. The main task ending, being canceled, or failing may also stop related subtasks; work and outputs already done will not be automatically revoked. Subtask failures should be retained as unfinished items and must not be silently rewritten by the main task as "no issues found."