> For the complete documentation index, see [llms.txt](https://help.docupilot.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.docupilot.app/workflows/troubleshoot-workflows.md).

# Troubleshoot Workflows

Start with the **Findings** menu for build or publish problems. For execution problems, open **Workflow runs**, select the failed run, and inspect the failed module.

| Problem                             | What to check                                                                                                          |
| ----------------------------------- | ---------------------------------------------------------------------------------------------------------------------- |
| A form field is unavailable         | Update and publish the selected form from Extensions, then reopen the affected workflow module.                        |
| A template contains the wrong value | Confirm that the template token is mapped to the intended form field.                                                  |
| A branch does not run               | Check the condition field, operator, comparison value, and submitted data. Confirm the outcome is connected.           |
| A module does not run               | Confirm it is connected after the required upstream module and belongs to the selected condition path.                 |
| A file is unavailable               | Confirm the source module runs earlier on the same path and produces the selected file.                                |
| A file type is unsupported          | Add a Convert module or select a supported file output.                                                                |
| The workflow cannot be published    | Open Findings and resolve every error. Confirm templates are published and every path ends in a delivery.              |
| Test Run is disabled                | Save the workflow, clear errors, and activate the workflow if it is inactive.                                          |
| A delivery fails                    | Inspect the delivery module's inputs and error. Check recipients, endpoint, account authorization, and selected files. |

## Save Succeeds but Publish Fails

Saving is designed to preserve work in progress. Incomplete modules and connections can therefore be stored with findings.

Publishing validates the complete executable workflow. It can be blocked by missing connections, invalid mappings, an unpublished form or template, unsupported files, or incomplete deliveries.

## A Condition Uses the Wrong Path

1. Open the run and verify the value received by the Form module.
2. Select the Condition module and review each non-default outcome.
3. Confirm the field, operator, and expected value.
4. Confirm the default outcome is connected.
5. Save and start another test run.

## A Delivery Fails

Select the failed delivery module in the run and review:

* the file inputs received by the module
* recipient, signer, or endpoint values
* connected delivery account status
* the complete provider error

Some email, webhook, and eSign provider errors are returned directly by the provider. Reauthorize an expired account or correct the provider configuration before testing again.

## A Downstream Module Is Skipped

A module can be skipped because its condition branch was not selected or because a required upstream module failed. Fix the first failed module on that path; skipped descendants do not need to be corrected individually.

Independent branches may still complete successfully.


---

# 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://help.docupilot.app/workflows/troubleshoot-workflows.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.