> For the complete documentation index, see [llms.txt](https://doc.wearepatchworks.com/product-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.wearepatchworks.com/product-documentation/process-flows/troubleshooting-process-flows/process-flow-not-running.md).

# Process flow not running

## Scenario

A process flow has been triggered (either manually, or via a trigger schedule, API call or webhook) but it's not running.

## Reason

* A process flow must be both deployed AND enabled to run according to its [trigger shape](/product-documentation/process-flows/building-process-flows/process-flow-shapes/standard-shapes/trigger-shape/trigger-shape-schedule.md) settings. 
* When a process flow is triggered to run it is placed in a queue for processing as soon as possible. Sometimes the run will happen immediately but other times there may be a short wait, depending on how many jobs are running at the time.

## Solution

* Check [which version of the process flow is deployed](/product-documentation/process-flows/building-process-flows/process-flow-versioning.md) - does it include the correct trigger shape settings? If not, you may have a draft version waiting to be deployed - or you may need to update and deploy a new draft.  
* Check that the process flow is [enabled](/product-documentation/process-flows/managing-process-flows/enabling-and-disabling-a-process-flow/enabling-and-disabling-a-process-flow-without-virtual-enviroments.md).
* Check your [run queue](/product-documentation/process-flows/error-reporting-and-exception-handling/run-logs-and-queue.md) for pending jobs. If you see an entry for this run then no action is required - it will be started as soon as possible. If you don't see a pending entry, check the [run logs](/product-documentation/process-flows/error-reporting-and-exception-handling/run-logs-and-queue.md#working-with-run-logs) in case the job has already been completed. 
* If there is no associated entry in your queue or logs and your process flow is deployed & enabled, please [contact Patchworks support](/product-documentation/raising-a-support-ticket.md) for assistance.

## Further information

For more information please see the following pages:

* [Process flow versioning](/product-documentation/process-flows/building-process-flows/process-flow-versioning.md) 
* [Enabling & disabling a process flow](/product-documentation/process-flows/managing-process-flows/enabling-and-disabling-a-process-flow/enabling-and-disabling-a-process-flow-without-virtual-enviroments.md)
* [Run logs & queue](/product-documentation/process-flows/error-reporting-and-exception-handling/run-logs-and-queue.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://doc.wearepatchworks.com/product-documentation/process-flows/troubleshooting-process-flows/process-flow-not-running.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.