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

# Limits

> Overview of resource limits on Nango Cloud.

Nango Cloud has several resource limits to ensure platform stability and fair usage across all customers.

<Note>
  For plan-specific limits, refer to the [pricing page](https://www.nango.dev/pricing) and the Usage & Billing page in your account.
</Note>

## API rate limits

Rate limits apply to API requests from your application to Nango:

| Plan       | Requests per Minute |
| ---------- | ------------------- |
| Free tier  | 200                 |
| Starter    | 1,000               |
| Growth     | 2,000               |
| Enterprise | Custom              |

<Info>
  If you exceed the rate limit, use the standard rate-limit headers to determine when to resume requests.
</Info>

## Function execution limits

Different function types have varying execution and enqueuing time limits:

| Function Type                                            | Max Execution Time |
| -------------------------------------------------------- | ------------------ |
| [Sync functions](/guides/functions/syncs/sync-functions) | 24 hours           |
| [Action functions](/guides/functions/action-functions)   | 15 minutes         |
| [Webhook functions](/guides/functions/webhook-functions) | 1 hour             |

### Minimum sync frequency

For polling syncs, the minimum frequency is **30 seconds**, available on all plans. You can set the frequency in the sync definition or override it per connection using the [SDK](/reference/backend/backend-sdk/node#override-sync-connection-frequency) or [API](/reference/backend/http-api/sync/update-connection-frequency).

For real-time updates, use [real-time syncs](/guides/functions/syncs/realtime-syncs) which trigger from external API webhooks instead of polling.

### Sync variant limits

Each sync can have a maximum of **100 variants** per connection. For heavier workloads, reach out to increase this limit. See the [sync partitioning guide](/guides/functions/syncs/sync-partitioning) for more details.

### Action function output limits

Action functions have a maximum output payload size of **2MB**. For large payloads, use the [Proxy](/guides/platform/proxy-requests) instead.

## Data retention policies

Nango automatically manages data retention for records in the sync cache:

### Payload pruning (30 days)

If a record hasn't been updated for **30 days**, Nango automatically prunes its payload while preserving:

* Record ID
* Sync state
* Payload hash (for change detection)

The record still exists and Nango can detect future changes, but the data fields are no longer retrievable from the cache.

### Hard deletion (60 days)

If a sync hasn't executed for **60 days**, all associated records (payload + metadata) are permanently deleted.

<Note>
  These policies ensure sensitive data isn't stored indefinitely. If you need to access record payloads long after updates (30+ days), please reach out in the [Slack community](https://nango.dev/slack).
</Note>

## Webhook limits

Webhooks sent from Nango to your application have the following limits:

* **Timeout**: 20 seconds
* **Retries**: 2 attempts

These limits apply to all webhook types: auth, sync function completion, async action function completion, and webhook forwards.

## Related guides

* [Rate limits](/guides/functions/rate-limits) - handle provider throttling in functions.
* [Sync efficiency](/guides/functions/syncs/sync-efficiency) - stay within payload and runtime limits.
* [Security](/guides/platform/security) - review retention and access constraints.

<Tip>
  **Questions, problems, feedback?** Please reach out in the [Slack community](https://nango.dev/slack).
</Tip>