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

# Manage Runs & their Status

> This guide explains the different Run (Job) statuses in Captain Data and how to manage them.

## **Run Statuses**

<Info>
  In Captain Data, Runs (formerly called "Jobs") can have various statuses
  indicating their current state. This guide explains each status, what it
  means, and how to manage runs effectively.
</Info>

### 🔁 1. **Running**

Indicates that the run is actively processing data.

* **What to do:** No action is needed—just wait for the run to complete.
* **Important Notes** -- If the run remains in this status for a long time, check whether:
  * You have been rate limited by our system ([check here rate limitations that apply to your plan](/v3/runs/inputs-processing#rate-limiting-on-parallel-inputs)), causing the run to be paused. When using the API you will receive a **429 error** which you’ll need to handle if you want your jobs to continue.
  * You’ve configured **specific scheduling options** or **Eligible times** for the run.

**Resolution Steps:**

* Review your schedules and limits.
* Stop your rescheduled Run by using [DEL - Remove a Schedule](/v3/api-reference/runs/remove-schedule) and Launch your workflow again with the new schedule settings.

For more guidance:

* [Manage Schedules](/v3/runs/manage-schedules)
* [Launcher Settings: Advanced Scheduling Options](https://support.captaindata.com/en/articles/10725086-launcher-settings-advanced-scheduling-options)

### ✅ 2. **Finished**

🎉 The run completed successfully, and all steps executed as expected.

* **What to do:** Celebrate! The success webhook has been triggered
* You can use [GET - Get a Run’s Results](/v3/api-reference/runs/get-job-results) to retrieve your run results

### ⚠️ 3. **Warning**

One or more steps in the run encountered a functional error (e.g., bad input, invalid parameter, etc.).

**What to do:**

* Check your failed webhook to have more information on the error
* Use the [POST - Retry a Run](/v3/api-reference/runs/retry-job) endpoint to reprocess the failed step

### ❌ 4. **Shutdown**

The automation encountered a technical error, often from a third-party API or our internal system.

**What to do:**

* Check your failed webhook to have more information on the error
* Use the [POST - Retry a Run](/v3/api-reference/runs/retry-job) endpoint to reprocess the failed run
* Contact our team if the error persists

### ⛔ 5. **Stopped**

The run was manually stopped by your team or you used the [POST - Cancel a Run](/v3/api-reference/runs/cancel-job) endpoint.

**What to do:**

* Use the [POST - Retry a Run](/v3/api-reference/runs/retry-job) endpoint to reprocess the run

### ⏸️ 6. **Paused**

The run paused due to issues like invalid cookies, insufficient credits, or outdated API keys.

**What to do:**

* Either you individually refresh the account(s) of your paused Run and retry it
* Or you can refresh and retry in bulk using the [POST - Add or Update Integration Account](/v3/api-reference/integrations/add-update-account)
  endpoint by passing the parameter `resume_paused_jobs` to `true`

## **General Tips for Managing Runs**

* **Inspect Errors Quickly**: Always refer to the status and error message of your run for actionable insights
* **Retry Strategically**: Implement a retry only when inputs were corrected or the issue has been resolved
* **Contact Support**: If you encounter persistent issues, don't hesitate to reach out. We're here to help! 💪