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

# Jobs

> Learn how to run workflows and track results in Opus.

A Job is what happens when you run a workflow. You provide inputs, Opus runs through the workflow steps, and you get outputs.

## What Is A Job?

When you run a workflow, you create a job. Here's what that means:

| What you get                | Why it matters                                                              |
| --------------------------- | --------------------------------------------------------------------------- |
| **Your inputs are saved**   | You can always see what data you started with                               |
| **Locked workflow version** | The job runs exactly the workflow you activated—later edits don't affect it |
| **Results are stored**      | Access your outputs anytime, even months later                              |
| **Full history**            | Everything is logged so you can review or audit later                       |

<Note>
  Jobs are different from Builder previews. Jobs are production runs that are tracked and saved for future reference.
</Note>

## Creating And Running Jobs

### From The UI

<Steps>
  <Step title="Go to Jobs">
    Click **Jobs** in the sidebar, or click **New Job** from the workflow details page of any active workflow.
  </Step>

  <Step title="Pick a workflow">
    If you started from the Jobs page, select an active workflow from the dropdown. This step is skipped if you started from a workflow details page.
  </Step>

  <Step title="Enter your inputs">
    Fill in the required fields. These match the inputs you defined in your workflow.

    <Info>
      For file inputs, you can upload directly or pull from connected integrations. This depends on your workflow design.
    </Info>
  </Step>

  <Step title="Run it">
    Click **Execute Job**.
  </Step>

  <Step title="Watch it run">
    Track progress in the Jobs dashboard. You can see which steps are running and when they complete.
  </Step>
</Steps>

### From The API

You can also start jobs programmatically. This is useful for running jobs on a schedule, automating recurring processes, or triggering workflows from your own applications.

See the [API Reference](/api-reference/introduction) for full details.

## Job Status And Monitoring

### Status Indicators

Jobs show clear status indicators as they run:

* **In Progress**: Actively working through the workflow steps
* **Completed**: Everything finished without errors
* **Failed**: Something went wrong—you'll see which step failed and why

### Viewing Job Details

On the Job Details page, you can see:

* **Inputs**: What you provided when you started the job
* **Outputs**: The results (if the job completed)
* **Timeline**: When each step started and finished
* **Errors**: What went wrong (if it failed)
* **Audit log**: The complete record of everything that happened

## Error Handling

### Common Problems And Fixes

<AccordionGroup>
  <Accordion title="Integration login expired">
    **What happened**: Your connection to an external service (like Google or Slack) expired.

    **Fix**: Go to integrations settings, reconnect the service, and re-run the job.

    **Prevent it**: Test your integrations in Builder preview before activating.
  </Accordion>

  <Accordion title="Rate limit hit">
    **What happened**: An external API blocked you for making too many requests.

    **Fix**: Wait a few minutes and try again.

    **Prevent it**: Space out your API calls or process data in smaller batches.
  </Accordion>

  <Accordion title="Wrong input type">
    **What happened**: You provided data in the wrong format (like text instead of a number).

    **Fix**: Check what type of input the workflow expects and provide the right format.

    **Prevent it**: Test your inputs in Builder preview before activating.
  </Accordion>

  <Accordion title="File too large">
    **What happened**: You uploaded a file that exceeds the 10 MB size limit.

    **Fix**: Reduce the file size (compress, split, or remove unnecessary content) and try again.

    **Prevent it**: Check file sizes before uploading. The maximum file size for uploads is 10 MB per file.
  </Accordion>
</AccordionGroup>

### Where Errors Appear

Errors are shown in three places on the Job Details page:

1. **On the failed step**: The specific step that failed is marked with an error message
2. **On the job**: The overall job shows as Failed with a summary
3. **In the audit log**: Full details for deeper investigation

<Tip>
  Start by finding which step failed, then read its error message. That usually tells you exactly what went wrong.
</Tip>

## Jobs And Subworkflows

When your workflow calls another workflow:

* The job runs both the main workflow and the sub-workflow
* Both must be active and in the same workspace
* You can see results from both in the job details

## Best Practices

### Before Running

* **Make sure the workflow is active** — Draft workflows can't run jobs
* **Test in Builder first** — Catch problems before running production jobs
* **Check your integrations** — Make sure connections haven't expired

### While Running

* **Watch for stuck jobs** — If a job seems frozen, check for errors
* **Don't run duplicates** — Wait for a job to finish before starting another with the same inputs

### After Completion

* **Check your results** — Make sure the outputs look right
* **Review failures** — Use error details to fix problems in your workflow

## Related Resources

<CardGroup cols={2}>
  <Card title="Workflows" icon="diagram-project" href="/guides/workflows">
    Design the automation logic that jobs execute.
  </Card>

  <Card title="Builder" icon="hammer" href="/guides/builder">
    Test workflows with previews before production jobs.
  </Card>

  <Card title="API Reference" icon="code" href="/api-reference/introduction">
    Trigger and monitor jobs programmatically.
  </Card>

  <Card title="Workspaces" icon="folder-tree" href="/guides/workspace">
    Manage job access across your team.
  </Card>
</CardGroup>