> For the complete documentation index, see [llms.txt](https://docs.durohub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.durohub.com/advanced-topics/error-handling.md).

# Error Handling

Learn how to handle errors and edge cases in the Duro API.

### Error Types

The API returns different types of errors:

* Validation errors
* Authentication errors
* Authorization errors
* Rate limiting errors
* Server errors

### Error Format

```graphql
{
  "errors": [
    {
      "message": "Not authorized to access Component",
      "path": ["component"],
      "extensions": {
        "code": "FORBIDDEN",
        "classification": "AuthorizationError"
      }
    }
  ]
}
```

### Common Error Scenarios

```graphql
# Rate Limiting Error
{
  "errors": [
    {
      "message": "Rate limit exceeded",
      "extensions": {
        "code": "RATE_LIMITED",
        "retryAfter": 60
      }
    }
  ]
}
```

### Best Practices

* Implement proper error handling
* Add retry logic for rate limits
* Log errors for debugging
* Handle network timeouts
* Provide user-friendly error messages

### Error Recovery

```typescript
async function queryWithRetry(query: string, maxRetries = 3) {
  for (let attempt = 1; attempt <= maxRetries; attempt++) {
    try {
      return await executeQuery(query);
    } catch (error) {
      if (!isRetryableError(error) || attempt === maxRetries) {
        throw error;
      }
      await delay(exponentialBackoff(attempt));
    }
  }
}
```

### Next Steps

Join our [Developer Community](/community/developer-community.md) for support and discussions.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.durohub.com/advanced-topics/error-handling.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.