If your Automation run shows a failure in the Run History, here’s how to troubleshoot and share the right info with our team:
Step-by-Step Troubleshooting
1. Use “Run Test” for quick diagnosis
Each Trigger and Action supports a “Run Test” function. It’s a good first step to catch major config errors — though passing a test doesn’t guarantee it will run successfully in a live flow.
2. Check Run History for failure clues
Click into the failed run to see where the error occurred and what was returned.
Look at:
- Input: what data was sent into this step
- Output: what result came out of this step
- Records: how many records the step operated on
This will often reveal whether it was a config issue, a missing variable, or a failed data fetch.
If You Can’t Spot the Issue
If you’ve reviewed the above but still can’t find the cause, we’re happy to help — here’s what to send us:
-
A full screenshot of your automation flow (or at least the relevant step)
-
The output and input from each step (the more, the better)
-
A short screen recording is super helpful, especially if the issue is hard to explain or intermittent
What If the Run Succeeds but Nothing Happens?
Sometimes your automation says “Success” but doesn’t do what you expect. This is often due to config or variable issues.
Try:
- Running a Run Test on each step individually
- Double-checking variable mappings
- Reviewing output fields in Run History — look for null or missing data
- Then re-run the automation after making changes
Example case:
A user reported a successful email send log, but the email wasn’t actually delivered and the counter stayed at 0.
See here: Is Bika’s Email Hosting Service Not Working?
We’re always here to help. The more details you can share, the faster we can assist! 
You can post your issue in the community.
