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

# Run history

> Detailed log of every run, debug, retry, export.

Every workflow execution is tracked in **Run history**. Here you debug issues, see performance, retry failed runs.

<Frame>
  <img src="https://mintcdn.com/agevole/BUuJGD62nuns4mJL/images/automazioni/en/run-history.svg?fit=max&auto=format&n=BUuJGD62nuns4mJL&q=85&s=9f8b07590beb25258947f0e544154331" alt="Run history table with timestamp, status, duration per run" width="1200" height="720" data-path="images/automazioni/en/run-history.svg" />
</Frame>

## Where to find it

**Automations → \[select workflow] → History tab**.

## Table columns

| Column           | Content                                |
| ---------------- | -------------------------------------- |
| Date/time        | Execution start timestamp              |
| Trigger          | Record or event that activated         |
| Status           | Success / Failed / Cancelled / Running |
| Duration         | Total execution time                   |
| Actions executed | X of Y total (if failed mid-way)       |
| User             | Who launched (for manual triggers)     |

## Filters

* **Status**: success only, failed only, etc.
* **Period**: today, week, month, custom range
* **Trigger**: per specific record or event type

## Run detail

Click a row opens the detail:

<AccordionGroup>
  <Accordion title="Actions timeline">
    Chronological list of every executed action, with duration and output.
  </Accordion>

  <Accordion title="Input/output per action">
    Expand each action to see: received input (from trigger or previous action), filled parameters, generated output.

    Useful for debugging: understand which action gets wrong data.
  </Accordion>

  <Accordion title="Resolved variables">
    See how `{{variables}}` were resolved at execution (actual values).
  </Accordion>

  <Accordion title="Error stack trace">
    If a run failed, Arya shows:

    * The failing action
    * Error type (timeout, API error, validation)
    * Detailed stack trace
    * Resolution suggestion
  </Accordion>
</AccordionGroup>

## Retry execution

For failed runs:

<Steps>
  <Step title="Open run detail">Click the failed row.</Step>

  <Step title="Retry">
    Click **Retry**. Options:

    * **Whole workflow**: rerun from scratch
    * **From action X**: restart from the failed action (useful if previous actions already had real effect)
  </Step>

  <Step title="Monitor">New run appears in history. If it fails again, Arya alerts you.</Step>
</Steps>

## Cancel execution

For **Running** but stuck runs (e.g. waiting for a webhook that never comes):

**⋯ → Cancel** → stops the run and frees resources.

## Aggregated metrics

**Metrics** tab of the workflow shows:

<CardGroup cols={2}>
  <Card title="Volume">Runs per day/week/month.</Card>
  <Card title="Success rate">% successes over total.</Card>
  <Card title="Average duration">Typical execution time.</Card>
  <Card title="Top errors">Most frequent error types (for priority debugging).</Card>
</CardGroup>

## Failure rate alerts

Configure from workflow settings:

* If failure rate > X% in last N runs → notify admin
* If average execution time increases by Y% → notify
* If 0 executions in expected period → "silent workflow" alert

## Log export

For audit or offline analysis:

* **Export CSV**: run table with metadata
* **Export JSON**: detailed log with input/output (sensitive data masked per policy)

Log retention:

* 30 days on Standard plans
* 180 days on Premium
* Unlimited (archiving) on Enterprise

## Frequently asked questions

<AccordionGroup>
  <Accordion title="Do logs include sensitive data like passwords?">No. Arya auto-masks fields recognised as sensitive (passwords, tokens, IBAN, tax codes).</Accordion>
  <Accordion title="Can I correlate logs across workflows?">Every run has a `correlation_id` that can be propagated to external systems (via webhook) for cross-system trace.</Accordion>
  <Accordion title="How do I monitor critical workflows?">Enable **Failure alerts** and add the workflow to the **SLA dashboard** (Settings → Monitoring).</Accordion>
</AccordionGroup>