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

# FAQ

> Answers to frequently asked questions about the Edges API, including data retention, billing, and common usage questions.

## How long is run data kept?

Edges automatically archives run data after **90 days** to maintain optimal platform performance. Once archived, runs are no longer accessible via the API.

**Retention periods:**

* **Runs and Flow Runs**: 90 days
* **Usage Records**: 5 days
* **Output Statistics**: 90 days

<Warning>
  If you need to keep run data longer than 90 days, make sure to store results in your own system via callbacks or export important data before the retention period expires.
</Warning>

<Warning>
  Outputs are **not available** for runs executed in `live` mode. It only works for runs executed in `async` or `schedule` mode. For live mode runs, results are returned directly in the API response.
</Warning>

For more details, see the [Data Retention section](/v1/runs/manage#data-retention) in the Managing Runs guide.

***

## How to track credits consumption?

To monitor your workspace's credit consumption, you can use the [Credit Consumption](/v1/api/workspace/consumption) endpoint.
This endpoint provides detailed information about the credits used during the current billing period, grouped by action.

It takes no parameters (always returns current billing period usage) and returns a breakdown of credit usage, allowing you to track your workspace consumption effectively.

Example response:

```json theme={null}
{
    "credits_left": 16689.1,
    "credits_used": 3310.9,
    "credits_max": 20000,
    "current_month_start": "2025-10-14T07:13:47.000Z",
    "current_month_end": "2025-11-14T07:13:47.000Z",
    "consumptions": [
        {
            "action_slug": "linkedin-extract-people",
            "credits_used": 112
        },
        // ... truncated for brevity ...
        {
            "action_slug": "linkedin-connect-profile",
            "credits_used": 90
        }
    ]
}
```

<Info>
  It retrieves only data for actions that have been used in the current billing period (don't forget **decimal values are possible**).
</Info>

***

## Troubleshooting & Errors

For comprehensive error handling guidance, including:

* Error response structure and scopes
* Quick reference table of all error labels
* Handling 429 (rate limit) and 424 (LinkedIn) errors
* Detailed documentation for each error type

<Card title="Error Reference" icon="triangle-exclamation" href="/v1/error-reference">
  Complete guide to understanding and handling all API errors
</Card>

***

## Rate Limits

For information about rate limits and best practices:

<CardGroup cols={2}>
  <Card title="API Rate Limits" icon="gauge-high" href="/v1/runs/rate-limits">
    Edges API request limits by plan tier
  </Card>

  <Card title="LinkedIn Smart Limits" icon="shield" href="/v1/linkedin/limits">
    How Edges protects LinkedIn accounts from restrictions
  </Card>
</CardGroup>