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

# Connector Backoff

> How CData Arc's connector backoff mechanism works, what triggers it, how to identify it, and how to resolve it.

export const siteNameShort = "Arc";

export const siteName = "CData Arc";

When a connector fails to send files repeatedly during automated processing, {siteNameShort} enters a **backoff state** for that connector. In backoff, the automation service temporarily pauses send attempts for the affected connector, giving you time to correct the underlying issue while protecting system performance.

## What Triggers Backoff

Backoff is triggered when a connector fails to successfully send any files across three consecutive automation cycles. A single failed file in an otherwise successful cycle does not trigger backoff; all files in the cycle must fail.

## How the Delay Works

Once a connector enters backoff, the automation service skips it for an escalating delay period:

| Failure round         | Delay before next attempt                      |
| --------------------- | ---------------------------------------------- |
| First                 | 60 minutes                                     |
| Second                | 120 minutes                                    |
| Each subsequent round | Increases further, up to a maximum of 12 hours |

The delay resets if the connector successfully exits backoff.

## Identifying Backoff

### UI Indicator

When a connector is in backoff, it displays a status indicator showing that it is in a backoff state and when the automation service is next scheduled to run. This indicator updates automatically when the backoff state changes, such as after a successful manual send or a settings save.

<img src="https://mintcdn.com/cdata-arc/OPGQ97w9DtgBQbbJ/public/images/connector-backoff.png?fit=max&auto=format&n=OPGQ97w9DtgBQbbJ&q=85&s=6ed4c0b2401e5e06e848e001cb6c5d84" alt="A connector showing a backoff status indicator" width="700" data-path="public/images/connector-backoff.png" />

### Application Log

{siteNameShort} writes a warning to the [application log](../getting-started/administration/activity#application-logs) when a connector enters backoff:

*This connector has failed \[# of times] and has entered a backoff state. The automation service will skip this connector until \[date/time]. The connector will remain in the backoff state until a message is successfully sent or received manually, the connector settings change, or all messages are sent successfully during an automated send attempt.*

### Unsent Files

If files are accumulating in a connector's **Transactions** tab with a status of Unsent while automation appears to be enabled, backoff is a likely cause. Check the application log for a backoff warning and review the transaction log for consecutive automation failures.

## Exiting Backoff

A connector exits backoff automatically when any of the following occurs:

* A file is sent or received successfully through a manual send or receive
* The connector's settings are saved
* All files are sent successfully during an automated send attempt

## Why Backoff Exists

Without backoff, a connector experiencing persistent failures (a misconfigured endpoint, an expired certificate, a network outage) would continuously retry, generating large numbers of failure log entries and database records. Over time, this degrades application performance. Backoff limits that impact while keeping the connector ready to recover as soon as the issue is resolved.