> For the complete documentation index, see [llms.txt](https://docs.skyone.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.skyone.cloud/english/skyone-studio/integrations/flows/flow-management/flow-canva-configuring-and-editing-the-flow/exception-handler/exception-handler-cases.md).

# Exception Handler - Cases

"**Exception Handlers"** can be used to solve many common situations. Here we list some of them and their possible solutions

***

#### Too Many Request - Status Code 429 <a href="#too-many-request-status-code-429" id="too-many-request-status-code-429"></a>

Many APIs implement rate-limit mechanisms that specify a maximum number of requests that can be executed in a given time period. Through an Exception Handler we can adjust the operation of a flow to stay within the defined rate.

The flow below accesses an API hundreds of times that is configured to accept a maximum of 10 requests per minute.

<figure><img src="/files/PpCUT3qUmTyuWZGBwfgh" alt=""><figcaption></figcaption></figure>

We set up an "**Exception Handlers"** for this flow with the following characteristics:

* Name: Too Many Requests
* Scope: Flow

**Exception Rule: 429 Too Many Requests**

* Name: 429 Error Code
* Retries: 2. At first only one retry would be enough, but we set two as safety margin.
* Seconds: 60. The API in question releases tokens every minute, so we wait a full minute until we restart the requests.
* Notification to syslog and local. It's important to be able to audit and track when we're exceeding the usage rates of an API
* Message: Too many requests - RETRY

**Default Action**

* Notification to syslog and local.
* Message: Too many requests - FATAL. In this case we can identify that despite the exception handling the error persisted.
* Final Action: **Stop**. This action will be taken only if the strategy of waiting for new tokens fails, which indicates that there is some unexpected situation that caused this error.

<figure><img src="/files/GfWb5P8nP1hSVCkziEMH" alt=""><figcaption></figcaption></figure>

This strategy guarantees correct API usage if only one execution of this stream occurs at the same time. To force this situation you can disable concurrent flow executions as illustrated below.

<figure><img src="/files/zAXgMAcqporSpxJOXKVs" alt=""><figcaption></figcaption></figure>


---

# 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.skyone.cloud/english/skyone-studio/integrations/flows/flow-management/flow-canva-configuring-and-editing-the-flow/exception-handler/exception-handler-cases.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.