Overview
Nova Act provides a comprehensive error hierarchy that helps you handle different failure scenarios appropriately. Understanding the error types allows you to implement robust retry logic and graceful failure handling.Error Hierarchy
All Nova Act errors inherit fromActError, which provides metadata about the failed operation:
Error Categories
ActAgentError
ActAgentError
Indicates the requested prompt cannot be completed in the given configuration. You may retry with a different request.Subclasses:
ActInvalidModelGenerationError- Model output could not be processedActInvalidToolError- Model attempted to call unknown toolActInvalidToolSchemaError- Tool call failed schema validationActAgentFailed- Agent raised an error because task was not possibleActExceededMaxStepsError- Exceeded maximum allowed stepsNoHumanInputToolAvailable- Model requested human input but no callbacks provided
ActExecutionError
ActExecutionError
Indicates a local error encountered while executing valid output from the agent.Subclasses:
ActActuationError- Failed to actuate a command from the agentActToolError- Failure running a toolActMCPError- Failure running an MCP-provided toolActCanceledError- User canceled executionApproveCanceledError- Canceled during human approvalUiTakeoverCanceledError- Canceled during UI takeoverActStateGuardrailError- Blocked by state guardrail
ActClientError
ActClientError
Indicates a bad request to NovaAct Service. You may retry with a different request.Subclasses:
ActBadRequestError- Bad request to /step endpointActGuardrailsError- Request blocked by agent guardrailsActRateLimitExceededError- Request throttled due to quota limitsActRequestThrottledError- Too many requests in short time periodActDailyQuotaExceededError- Daily quota exceeded
ActServerError
ActServerError
Indicates the NovaAct Service encountered an error. Report to customer support.Subclasses:
ActBadResponseError- Bad response from /step endpointActServiceUnavailableError- Service currently unavailableActInternalServerError- Internal server error occurred
Basic Error Handling
Catch All Act Errors
Handle Specific Errors
Retry Patterns
Simple Retry
Retry with Exponential Backoff
Conditional Retry
Retry with Alternative Prompts
Workflow-Level Error Handling
Handle Workflow Errors
Circuit Breaker Pattern
Timeout Handling
Set Act Timeout
Set Max Steps
Logging Errors
Log to File
Structured Error Reporting
Best Practices
Categorize Errors
Handle different error categories appropriately:
- AgentError: Revise prompt or break into smaller steps
- ClientError: Check input or wait for rate limits
- ServerError: Report to support
- ExecutionError: Check local environment
Use Exponential Backoff
Implement exponential backoff for retries:
Set Reasonable Limits
Configure appropriate timeouts and max steps:
Log for Debugging
Always log errors with context:
Troubleshooting Common Errors
ActExceededMaxStepsError
ActExceededMaxStepsError
Cause: Task requires more steps than allowedSolutions:
- Break task into smaller
act()calls - Increase
max_stepsparameter - Provide more specific prompts
- Add hints to guide the agent
ActRateLimitExceededError
ActRateLimitExceededError
Cause: Too many requests in short timeSolutions:
- Implement exponential backoff
- Reduce request rate
- Consider upgrading to AWS Nova Act service
ActInvalidModelGenerationError
ActInvalidModelGenerationError
Cause: Model produced invalid outputSolutions:
- Simplify the prompt
- Use more specific instructions
- Retry with alternative prompt
- Check if schema is too complex
ActStateGuardrailError
ActStateGuardrailError
Cause: Agent attempted to access blocked URLSolutions:
- Review guardrail configuration
- Add required domains to allowlist
- Adjust prompts to avoid blocked sites
Next Steps
Logging & Traces
View detailed traces to debug errors
Deployment
Handle errors in production deployments
Parallel Sessions
Error handling for concurrent workflows
Security
Handle security-related errors