> ## Documentation Index
> Fetch the complete documentation index at: https://docs.blinkops.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Error Handling

> Common errors when working with Blink agents and how to troubleshoot configuration and environment issues.

As with any powerful AI automation tool, occasional errors can occur when working with Agents, often due to configuration issues, environment settings, or external dependencies. To help you move past these quickly and confidently, we've outlined the most common errors, what they mean, and how to resolve them. This guide is designed to make your experience with Blink Agents as smooth and productive as possible, even when something unexpected comes up.

Below, you will find a list of the most common errors along with suggested remediation steps:

## Rate Limit Errors

<CardGroup cols={2}>
  <Card title="Error Message" icon="circle-1">
    *"You've reached the maximum number of **requests** allowed for running agents on this tenant. Please try again in `{next_window}`."*
  </Card>

  <Card title="Suggestion" icon="circle-1">
    This error occurs when the number of agent run requests has exceeded the permitted limit for the tenant within a fixed time window. This request [rate limit](/docs/agent-builder/limitations#rate-limits) ensures fair usage and system stability. Wait `1-minute`, then retry the request.
  </Card>
</CardGroup>

***

<CardGroup cols={2}>
  <Card title="Error Message" icon="circle-2">
    *"Rate limit exceeded: 1-minute data processing limit reached. Retry in one minute."*
  </Card>

  <Card title="Suggestion" icon="circle-2">
    This error indicates that the tenant has consumed the maximum number of agent execution requests within `1-minute` window. Wait `1-minute` to resume execution or review usage patterns. For additional information, navigate to the [rate limits](/docs/agent-builder/limitations#rate-limits) section.
  </Card>
</CardGroup>

<CardGroup cols={2}>
  <Card title="Error Message" icon="circle-2">
    *"Rate limit exceeded: 60-minute data processing limit reached. Retry in a few minutes."*
  </Card>

  <Card title="Suggestion" icon="circle-2">
    This error indicates that the tenant has consumed the maximum number of agent execution requests within the `60 minute` window. Wait a few minutes to resume execution or review usage patterns. For additional information, navigate to the [rate limits](/docs/agent-builder/limitations#rate-limits) section.
  </Card>
</CardGroup>

***

## Abilities Errors

<CardGroup cols={2}>
  <Card title="Error Message" icon="circle-3">
    *"The agent exceeded the maximum limit of `20` abilities executions in a single run."*
  </Card>

  <Card title="Suggestion" icon="circle-3">
    Refine the agent task so the agent processes fewer items in a single run. For example, if the agent is analyzing IP addresses, provide a smaller subset at a time (e.g., batch them in groups of 5–10 instead of sending all 20 at once). This helps keep the number of ability executions within the allowed limit.
  </Card>
</CardGroup>

***

<CardGroup cols={2}>
  <Card title="Error Message" icon="circle-4">
    *"Ability execution output is too long. Maximum size allowed is `100KB`."*
  </Card>

  <Card title="Suggestion" icon="circle-4">
    This error indicates that the output generated after running the agent step exceeded the maximum allowed size of `100KB`. Here’s a rewritten, suitable remediation: Review the ability used in the agent step and adjust how it is configured to generate only the essential data needed for your outcome. This may involve refining prompts and filtering unnecessary detail so the resulting abilities output remains within the `100KB` size limit.
  </Card>
</CardGroup>

***

<CardGroup cols={2}>
  <Card title="Error Message" icon="circle-5">
    *"Ability execution failed: `{workflow_name}`. Please try again or contact support if the issue persists."*
  </Card>

  <Card title="Suggestion" icon="circle-5">
    A specific ability (workflow) failed during execution. This is typically caused by internal processing errors, misconfiguration, or connectivity issues. Check the workflow setup and logs for more details.
  </Card>
</CardGroup>

***

## Other

<CardGroup cols={2}>
  <Card title="Error Message" icon="circle-6">
    *"The agent output structure exceeded the supported nesting depth of `3` levels."*
  </Card>

  <Card title="Suggestion" icon="circle-6">
    The agent's output includes a `JSON` structure nested deeper than three levels, which exceeds the supported depth. To resolve, [simplify the output](/docs/agent-builder/building-the-agent#json-output-format-phishing-email-example) to meet the depth limit.
  </Card>
</CardGroup>

***

<CardGroup cols={2}>
  <Card title="Error Message" icon="circle-7">
    *"An unexpected error occurred while running the agent. Please try again or contact support if the issue persists."*
  </Card>

  <Card title="Suggestion" icon="circle-7">
    An uncaught exception occurred during agent execution. This may be due to an internal runtime issue. Retry the run, and if the problem persists, escalate for further investigation.
  </Card>
</CardGroup>

***