Document Requirements Agent Troubleshooting

Common Issues and Solutions

• Issue: Agent not responding or enabled
  Solution: Verify the is_doc_requirement_agent_enabled flag in system settings and check for any rate limit blocks.

• Issue: Incorrect rule generation
  Solution: Review natural language input for clarity and specificity. The agent relies on precise instructions to build rules. Refer to the Creating Document Requirement Rules section for examples.

• Issue: Rules not being applied to loads
  Solution: Ensure the rule is active and that the conditions (customer, load type, location, etc.) accurately match the load’s attributes. Confirm that the enforcing system is correctly integrated with the Document Requirements Agent.

• Issue: Agent provides unexpected responses
  Solution: Rephrase the query. The agent is conversational, but clear and concise language yields the best results.

Error Messages and Meanings

• "Hello, I am not enabled for this environment yet..."
  The agent is not activated. Contact the CSM.

• "FEATURE_LIMIT_REACHED"
  Usage limits for the agent have been exceeded.

• "CONTEXT_WINDOW_EXCEEDED"
  The conversation history is too long for the AI model to process. Start a new conversation.

• "TOKEN_USAGE_LIMIT_EXCEEDED"
  The account has reached its token usage limit.

• "ERROR_OCCURRED"
  A general error occurred. Try again or contact support.

When to Contact Support
Contact support when:

• Persistent issues with rule creation or management occur.

• The agent consistently fails to interpret requests.

• System-level errors not covered in this guide are encountered.

• Assistance with advanced integrations or custom configurations is needed.