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

# Individual Workflow Run History

> Monitor and review workflow execution history

Track workflow execution, review results, and debug issues. Every workflow run is logged with detailed step-by-step information.

***

## Viewing Workflow Runs

Access run history for any workflow:

<Steps>
  <Step title="Navigate to the workflow">
    Go to **Workflows** and select the workflow you want to review
  </Step>

  <Step title="Open the Runs tab">
    Click the **Runs** tab to see execution history
  </Step>

  <Step title="Browse run history">
    View all runs sorted by date, with status indicators for each
  </Step>

  <Step title="Click a run for details">
    Select any run to see step-by-step execution details
  </Step>
</Steps>

***

## Understanding Run Status

Each workflow run has a status indicating its current state:

| Status                  | Meaning                                   | What to do                                       |
| :---------------------- | :---------------------------------------- | :----------------------------------------------- |
| ✅ **Success**           | Workflow completed all steps successfully | Review outputs if needed                         |
| ❌ **Failed**            | One or more steps encountered an error    | Check error details and fix the issue            |
| ⏳ **Running**           | Workflow is currently executing           | Wait for completion                              |
| ⏸️ **Pending Approval** | Waiting for approver action               | Contact approvers if urgent                      |
| 🚫 **Denied**           | Approval was rejected                     | Review denial reason, adjust and retry if needed |
| ⏹️ **Cancelled**        | Run was manually cancelled                | No action needed                                 |

***

## Run Details

Click on any run to see detailed execution information:

### Run summary

* **Started at** - When the run began
* **Completed at** - When the run finished (or failed)
* **Duration** - Total execution time
* **Triggered by** - Who or what initiated the run
* **Status** - Overall result

### Step-by-step breakdown

Each workflow step is logged with:

* **Step name** - What action was performed
* **Status** - Success, failure, or skipped
* **Duration** - How long the step took
* **Input** - What data was passed to the step
* **Output** - What the step returned
* **Error** - Error message if the step failed

<Tip>
  Use the step-by-step breakdown to identify exactly where issues occurred. Failed steps show the specific error that caused the failure.
</Tip>

***

## Debugging Failed Runs

When a workflow fails, follow these steps to diagnose and fix the issue:

<Steps>
  <Step title="Identify the failed step">
    Open the run details and find the step marked as failed
  </Step>

  <Step title="Review the error message">
    Check the error details for:

    * API errors from connected applications
    * Invalid input values
    * Permission or authentication issues
    * Network or timeout errors
  </Step>

  <Step title="Check the inputs">
    Verify the inputs provided were valid:

    * Correct format (email, date, etc.)
    * Valid values (existing users, resources, etc.)
    * Required fields were populated
  </Step>

  <Step title="Review application status">
    Check if the target application is:

    * Available and responding
    * Properly connected to Serval
    * Permissions are still valid
  </Step>

  <Step title="Re-run or fix and retry">
    Either:

    * Re-run with corrected inputs
    * Fix the workflow logic and publish a new version
    * Contact support if the issue persists
  </Step>
</Steps>

### Common failure causes

<AccordionGroup>
  <Accordion title="Authentication errors">
    **Symptom:** "Unauthorized" or "Authentication failed" errors

    **Cause:** API credentials expired or were revoked

    **Fix:** Reconnect the application in Serval's integrations settings
  </Accordion>

  <Accordion title="Not found errors">
    **Symptom:** "Resource not found" or "User does not exist" errors

    **Cause:** The target resource (user, group, repo, etc.) doesn't exist

    **Fix:** Verify the input values are correct and the resource exists
  </Accordion>

  <Accordion title="Permission errors">
    **Symptom:** "Forbidden" or "Insufficient permissions" errors

    **Cause:** Serval's integration lacks permission for the requested action

    **Fix:** Update the integration's permissions in the connected application
  </Accordion>

  <Accordion title="Rate limiting">
    **Symptom:** "Rate limit exceeded" or "Too many requests" errors

    **Cause:** Too many API calls to the application in a short period

    **Fix:** Wait and retry, or spread out workflow executions
  </Accordion>

  <Accordion title="Timeout errors">
    **Symptom:** "Timeout" or "Request took too long" errors

    **Cause:** The target application took too long to respond

    **Fix:** Retry the run, or check if the application is experiencing issues
  </Accordion>
</AccordionGroup>

***

## Filtering and Searching Runs

For workflows with many runs, use filters to find specific executions:

* **Date range** - Filter by when the run occurred
* **Status** - Show only successful, failed, or pending runs
* **Triggered by** - Filter by who initiated the run

***

## Scheduled Workflow Runs

For scheduled workflows, the Runs tab shows:

* All scheduled executions that have occurred
* The next scheduled run time
* Whether scheduled runs are succeeding consistently

<Warning>
  If a scheduled workflow consistently fails, it will keep trying at each scheduled time. Review and fix failures promptly to avoid repeated errors.
</Warning>

***

## Exporting Run Data

Export workflow run history for reporting or compliance:

1. Navigate to the workflow's Runs tab
2. Apply any filters needed
3. Click **Export** or **Download**
4. Choose your format (CSV, JSON)

Exports include:

* Run timestamps
* Status
* Duration
* Who triggered the run
* Input values
* Success/failure details

***

## Best Practices

<CardGroup cols={2}>
  <Card title="Monitor regularly" icon="eye">
    Check run history weekly to catch issues before they become problems
  </Card>

  <Card title="Set up alerts" icon="bell">
    Create a workflow that notifies you when other workflows fail
  </Card>

  <Card title="Review scheduled runs" icon="clock">
    Ensure scheduled workflows are running successfully on their expected cadence
  </Card>

  <Card title="Clean up old workflows" icon="broom">
    Disable or delete workflows that consistently fail or are no longer needed
  </Card>
</CardGroup>