# Workflow history and job states


> Read workflow-run progress and understand the statuses shown in history.


Canonical URL: https://www.copyhero.app/help/workflows/workflow-history-and-job-states

Use **Workflow History** to find a run, open it, and inspect product-level work.

<!-- screenshot: workflow-history-detail -->

## Find a run [#find-a-run]

1. Open **Workflows** and choose **Workflow History**.
2. Use **Search workflow, store, or product...** or filters to narrow the list.
3. Select a run to open its detail.
4. Select a product to inspect its jobs, activity, and available result details.

## Run titles [#run-titles]

Each run is titled automatically — a short, distinguishing name generated from
what you're importing, refreshed once the run finishes. You can rename any
run, including older ones, from its row actions menu in the list or from the
**Rename** button on the run's detail page; a manual title is never replaced
by a later automatic one.

## Read status [#read-status]

- **Pending**: the job is queued and has not started.
- **Running**: the job is being processed.
- **Finished**: the job completed.
- **Error**: the job failed and needs attention before a retry.
- **Cancelled**: the job was stopped and is terminal.

A run's status counts products, not jobs. A product counts as failed when one of its jobs has an error, even if its later steps never ran.

- **Running**: at least one product is being processed.
- **Cancelled**: the run was stopped before every product finished.
- **Error**: every product in the run failed.
- **Finished**: no product is still pending. When some products failed, an orange warning icon next to the status shows how many.
- **Pending**: products are still queued.

The progress bar shows finished products in green, failed products in red, and running products in blue. Hover it for the underlying job counts. On a run's detail page, select **Failed** above the product list, or the red failed count, to show only the products that failed.

## Run source and Monday updates [#run-source-and-monday-updates]

The small icon before the actions menu shows where a run came from: Monday.com, a webhook, or a manual start. Its colour shows how the run's Monday updates went: green when every update was written, orange when some failed, red when all failed, and grey when the run sent none. Hover the icon for the trigger name and the most common failure reason.

On a run's detail page, **Started by** names the Monday trigger; select it to see the trigger's board, event, and conditions. The summary counts failed Monday updates, and a red icon next to a product's status lists the updates that failed for it. If Monday access was revoked, a banner links to the Monday.com settings.

## Expected result [#expected-result]

You can identify the product and exact job that needs attention without recreating completed jobs.

## Errors and limits [#errors-and-limits]

History reflects the current run; editing a task or workflow does not rewrite it. The visible job labels can include internal execution steps such as loading, importing, or publishing; those are status details, not additional task types you can create.

## Related links [#related-links]

- [Retry failed jobs](/help/troubleshooting/retry-failed-jobs)
- [Workflow failures](/help/troubleshooting/workflow-failures)
- [Start a workflow](/help/workflows/start-workflow)