Auto AppyFor everyone6 min read
Troubleshooting
Start with History in the workflow editor: it shows whether the workflow ran and, for each step, what happened.
The workflow didn’t run at all
Section titled “The workflow didn’t run at all”Check these in order:
| Check | Fix |
|---|---|
| Is the workflow Live? The pill next to its name must say Live. | ⋯ → Workflow status → Live. |
| Is the trigger Live? | Capture a sample on the trigger, or set it Live from its panel. |
| Did the trigger receive anything? | Send a test (submit the form). For webhooks, check the sender really posts to Your Webhook URL. |
| Do you have tasks left? | Settings → Plan and usage. Top up if it’s at zero. |
| Is it a Schedule? | Check the times and time zone in ⋯ → Schedules & delays. |
Webhook responses
Section titled “Webhook responses”| Response | Meaning | Fix |
|---|---|---|
409 paused or in draft |
The workflow or that trigger isn’t Live. | Set both Live. |
200 Message data captured successfully |
The trigger was capturing a sample, so nothing ran. | Normal during setup. Send again to run for real. |
403 Insufficient task balance |
No tasks left. | Top up in Plan and usage. |
422 Add a workflow trigger… |
The workflow has no trigger. | Add one. |
404 |
Wrong URL or ID. | Copy Your Webhook URL again. |
| Browser shows a CORS error | A fetch() from another website was blocked by the browser. |
Post a plain HTML form, or call from your server. |
A step failed
Section titled “A step failed”Open the run in History and click the step to read the error.
| Error | What it means | Fix |
|---|---|---|
| Not connected / connection missing | The step has no account. | Setup → Existing Connection or connect one. |
| Required field missing | A required field is empty in this run. | Fill it, or map it, or add a condition so the step only runs when the value exists. |
401 / 403 from the app |
The saved account expired, or lacks permission. | Settings → App connections → Edit credentials, then retest. |
| This API key does not allow this operation | The connection uses a Read only key. | Replace it with a Read and write key. |
429 Too many requests |
The other app’s rate limit. | Add a Delay, or run less often. |
| Timeout | The other app took longer than 2 minutes. | Retry later; split big jobs into smaller ones. |
A step was skipped
Section titled “A step was skipped”Listed under Steps without results in a run. Usual reasons:
- the step is Draft or Paused: test it (a passing test makes it Live), or set it Live;
- a condition on the connection before it didn’t match: double-click the connection to check;
- it isn’t connected to the trigger at all: “This node is not connected to the starting step”. Connect it.
Mapping shows nothing
Section titled “Mapping shows nothing”- The trigger has no sample yet: Start Capturing Sample Data and send one submission.
- The earlier step hasn’t been tested: test it so it has output.
- The source step isn’t connected before this step on the canvas.
- Field names changed: re-capture the sample and update the mapping.
Dropdowns are empty
Section titled “Dropdowns are empty”Dropdowns (spreadsheet, WhatsApp number, CRM pipeline) load from your connected account. Connect the account on Setup first, then reopen Configure. For Google Sheets, only sheets created by or opened through Auto Appy are listed; tick Map Data and paste the sheet’s ID for others.
WhatsApp messages don’t arrive
Section titled “WhatsApp messages don’t arrive”- Starting a conversation needs an approved template (Send approved template). Plain text only works within 24 hours of the customer’s last message.
- Phone numbers need the country code without
+or spaces, such as919820012345. - The template’s language and variables must match exactly what Meta approved.
Still stuck?
Section titled “Still stuck?”- Ask Appy (bottom-right in the app): it can read the screen you’re on.
- Use Help in the left menu to reach the Auto Appy team. Say which app and workflow, what you did, and the exact error. Never include passwords or OTPs.
