> For the complete documentation index, see [llms.txt](https://docs.krystal.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.krystal.app/products/platform-config/automation-retry-policy.md).

# Automation Retry Policy

Defines Krystal’s retry mechanism for automation systems.

#### **Overview**

Automation systems on Krystal (such as Auto-Rebalance, Auto-Exit, Auto-Compound, and Auto-Harvest) include a built-in retry mechanism to improve reliability and ensure that scheduled actions are executed successfully, even under temporary network or on-chain disruptions.

#### Retry Rules

| Parameter                | Value        | Description                                                                                           |
| ------------------------ | ------------ | ----------------------------------------------------------------------------------------------------- |
| **Max Retry Attempts**   | 12           | Each automation order may be retried up to 12 times if execution fails due to transient errors.       |
| **Retry Interval**       | 5 minutes    | Between each retry, the system waits 5 minutes before re-attempting execution.                        |
| **Total Retry Duration** | \~60 minutes | In total, the system continues retrying for approximately 1 hour before the task is marked as failed. |

#### Design Rationale

This retry mechanism improves automation reliability under fluctuating network conditions while maintaining a bounded execution window.\
The 12×5-minute retry policy ensures:

* Timely completion under normal conditions
* Avoidance of indefinite looping or spam retries
* Predictable failure window (\~1 hour)

#### After Retry Window

If an automation still fails after the full retry period (\~60 minutes), it is marked as **failed**.\
To restore normal operation, users should:

* **Delete and re-create** the automation, or
* **Edit and update** the existing automation to trigger a new execution cycle.

This ensures the automation restarts with the latest market and pool data.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.krystal.app/products/platform-config/automation-retry-policy.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.