> For the complete documentation index, see [llms.txt](https://docs.notionapps.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.notionapps.com/automation/troubleshooting-automation/submit-button-troubleshooting.md).

# Submit Button Troubleshooting

## Submit Button Troubleshooting

Use this page when a user clicks Submit and the workflow does not start.

![Approval workflow setup showing When this happens.](https://content.gitbook.com/content/5ZqDXcVVffWUqEIZVhmn/blobs/kPhC9GrOLlzI30v2hkd5/assets/approval-management/maker-builder/03-procurement-approval-desk-approval-workflow-setup.jpg)

*The trigger must point to the real user action, not only a status value the maker changes manually.*

### The short answer

The submit button probably saves the record but is not connected to the workflow trigger, or the button writes a status value that the workflow is not listening for.

### Fix it step by step

1. Open Automation.
2. Select the workflow.
3. Find When this happens.
4. Select the actual submit button or form submission the user clicks.
5. Check the status the button writes.
6. Match the workflow submitted status to that exact value.
7. Save.
8. Run validation.
9. Create a new test request from the user-facing screen.
10. Confirm the destination screen receives the item.

### Do not use this as proof

Manual database changes are not proof that Submit works. A manual status change can start a workflow even when the user-facing button is broken. The test must use the same button the user will click.

### Signs the fix worked

* The requester sees Submitted or Waiting for review.
* The reviewer sees the item on Decision or Work Queue.
* The message or notification is delivered.
* Workflow Status changes.
* Exception Resolution has no unexpected failure.