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

# Monitor and troubleshoot workflow runs

> Inspect workflow runs, distinguish preview from execution, and check delivery attempts and failures.

Use **Evelin AI → Automations → Runs** to review activity across workflows. Open a workflow's **Activity** tab to focus on that workflow.

Select a run to open **Run details**. It shows the outcome, AI credits and operations, individual steps, and the event history.

## Preview, execution, and delivery

| What you did | What it proves |
| - | - |
| **Test workflow → Preview path** | Checks a path using current conversation data. It performs no actions and spends no credits. |
| **Run workflow** or an automatic/scheduled run | Executes the published workflow against eligible data. |
| A connector step completed | The step completed its work, which can include queuing a delivery. |
| The connector delivery succeeded | The receiving destination accepted the request. Check the destination for the intended result. |

A run can show **Steps completed** while a connector delivery is still queued, retrying, or failed. Open the relevant step to inspect delivery attempts, the last HTTP response when available, and the next retry time.

Run details refresh periodically. Select **Refresh** to request the latest result.

## If a workflow does not start

1. Check that it is **Published**.
2. Confirm that the selected trigger matches the event you are testing.
3. For scheduled workflows, check the frequency, time, timezone, and weekdays.
4. For manual workflows, save changes before using **Run workflow** on an eligible ticket.
5. Check workspace availability, AI credits, and reported permission or runtime errors.

Publishing does not replay old events. Create a new matching event after publication when testing an automatic workflow.

Scheduled and manual starts exclude test, archived, and merged conversations. A scheduled workflow can include resolved conversations, so add conditions when you want only open work.

## If a run stops or skips a step

Inspect the selected condition path, required configuration, and the step's event details. A non-matching condition can end a path normally.

A preview can stop at an AI-dependent decision or another step it cannot execute. **Not tested** in the preview is not proof that the live step failed.

For external requests, check the destination URL, credentials, response, and remaining retry attempts. Before starting another real run, check whether an earlier attempt already changed the destination.

## Stop or remove a workflow

Select **Unpublish** to stop new runs while you investigate. Completed ticket changes and external requests are not undone.

**More workflow actions → Duplicate workflow** creates a draft copy. Review it before publishing, especially if the original is still active.

**Delete workflow** unpublishes it and removes it from the workflow list. Deletion cannot be undone; past activity remains available in **Monitor**.

See [Build and publish a workflow](/guides/configure-ai-automation) to revise the configuration, and [AI credits](/guides/understand-ai-credits) for usage.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.