Retries

Overview

Retries tell CronFox to try the HTTP request again if a run fails. You control how many times to retry and how long to wait between attempts.

Defaults when retries are disabled: no automatic retries (retry_count effectively off). When enabled in the task form, you set retry count and retry delay (seconds).

Step-by-step

1. Open the task on its collection view (create or edit).
2. Expand advanced settings.
3. Enable retries.
4. Set retry count — how many additional attempts after the first failure.
5. Set retry delay — seconds to wait between attempts (default in the form is often 5).
6. Save, then trigger Run now against an endpoint you can force to fail once to confirm behavior.

How retries behave

1. CronFox performs the HTTP call.
2. On failure, if attempts remain, it waits for retry delay and tries again.
3. The execution outcome reflects the final result after retries are exhausted or a success occurs.

Exact attempt details appear in execution history for that run.

When to use

• Use retries for transient network errors or briefly overloaded APIs.
• Avoid aggressive retries on endpoints that are not idempotent (for example payments) unless the API is safe to call twice.
• Pair retries with failure notifications so you still hear about persistent outages.