Task Status
Understanding task statuses is crucial for monitoring, managing, and intervening in automated workflows. Each status represents a stage in the task lifecycle and indicates what actions may be required from you or the system.
Why Statuses Matter
- Clarity: Instantly see where tasks are in the workflow
- Action Guidance: Know what action is needed next
- Progress Tracking: Monitor completion and efficiency
- Issue Detection: Identify tasks needing attention
- Workflow Coordination: Align automated and human tasks
Key Statuses
In Queue
Status Code: IN_QUEUE
Tasks waiting for an agent to start processing.
Characteristics:
- Task is created, validated, and waiting
- No immediate user action required
User Actions:
- Monitor queue position
- Cancel task if no longer needed
- View task details
In Progress
Status Code: IN_PROGRESS
Tasks actively being executed by an agent.
Characteristics:
- Agent is processing the task step by step
- Real-time updates may be available
User Actions:
- Monitor progress
- View execution logs
- Prepare for human-in-the-loop interaction if requested
- Cancel task if necessary
Needs Assistance
Status Code: REQUIRES_ASSISTANCE
Agent requires human input to continue.
Characteristics:
- Task is paused until guidance is provided
- Agent presents options or context clearly
User Actions:
- Review context and problem
- Analyze available options
- Provide clear instructions or make decisions
- Add additional context if helpful
Common Scenarios:
- Ambiguous requests
- Conflicting or missing data
- Complex business logic requiring judgment
Approval Needed
Status Code: REQUIRES_APPROVAL
Tasks waiting for human permission to proceed.
Characteristics:
- Agent proposes an action and pauses
- Context and reasoning are provided
User Actions:
- Review proposed action and context
- Approve, Deny, Modify, or Request More Info
- Escalate if necessary
Examples:
- High-value refunds or purchases
- Critical system updates
- External communications requiring approval
Complete
Status Code: COMPLETE
Tasks finished successfully.
Characteristics:
- All objectives accomplished
- Outputs and logs are available
User Actions:
- Review results
- Provide feedback
- Request modifications or extend task
- Archive completed task
Follow-up Opportunities:
- Refine outputs
- Share learnings with team
- Apply successful patterns to new tasks
Cancelled
Status Code: CANCELLED
Tasks stopped before completion.
Characteristics:
- Execution intentionally stopped
- Partial work may exist
User Actions:
- Review partial results
- Understand reason for cancellation
- Restart if appropriate
- Clean up partial outputs
Common Causes:
- User request
- System or resource issues
- Dependency failures
Error
Status Code: ERROR
Tasks that encountered problems preventing completion.
Characteristics:
- Execution stopped due to technical or logical issues
- Error details provided
User Actions:
- Review error details and context
- Check configuration and inputs
- Fix underlying issues if possible
- Retry task or escalate to support
Common Error Types:
- Connection or API failures
- Permission or authentication issues
- Invalid or missing data
- Configuration mistakes
- Business logic violations
Troubleshooting Steps:
- Read the error message carefully
- Verify recent changes and inputs
- Check external system availability
- Review input data for accuracy
- Test with simplified parameters
- Contact support if needed
Status Transitions
Understanding how tasks move between statuses helps you anticipate what comes next:
Typical Flow:
In Queue → In Progress → Complete
With Human Interaction:
In Queue → In Progress → Approval Needed → In Progress → Complete
In Queue → In Progress → Needs Assistance → In Progress → Complete
Error Scenarios:
In Queue → Error (configuration issues)
In Progress → Error → In Queue (after fixes, retry)
In Progress → Error → Cancelled (unrecoverable)
User-Initiated Changes:
In Queue → Cancelled (user cancellation)
In Progress → Cancelled (user cancellation)
Approval Needed → Cancelled (denied approval)
Monitoring Tips
- Set up notifications for status changes needing attention
- Check high-priority tasks regularly
- Respond promptly to human-in-the-loop requests
- Track patterns in errors and task durations
