Even the best-built Workflow can occasionally misbehave. Have a read through the common issues below. Chances are, it is one of these.
My Workflow Isn’t Triggering
The most common culprit here is surprisingly simple: is the Workflow enabled?
It is an easy step to forget, and a disabled Workflow will sit there quietly doing absolutely nothing, no matter how perfect its logic is.
If it is enabled, double-check:
- The Listener node is set up to catch the correct event type.
- Any conditions attached are not unintentionally filtering the event out.
- The event you are expecting has actually occurred on the account. It sounds obvious, but it happens to the best of us.
My Workflow Triggered Twice
If a Workflow fires more than once for what feels like a single event, it is worth checking whether:
- Multiple triggering events are occurring in quick succession, such as a status flickering back and forth.
- The same event is being picked up by more than one Listener node.
- There is not a loop somewhere in your logic sending the Workflow back through itself.
A quick review of your node connections usually reveals the source of the déjà vu.
Why Didn’t My Email Send?
If your Email Notification node does not seem to be doing its job, check:
- The recipient details are correct and do not contain a stray typo.
- The node is correctly connected through the green ball and is not accidentally hanging off the red one.
- The Workflow actually reached that node. If an earlier condition was not met, the Email Notification node never gets its turn.
- Your spam or junk folder, just in case the email was sent and got waylaid en route.
Variables Are Empty
Empty variables are usually a sign that the data you are expecting is not available at the point the Workflow runs.
A few things to check:
- The variable is spelled and referenced correctly. Small typos are sneaky.
- The triggering event actually includes the data you are trying to use. Not every event carries every parameter.
- The variable is not being called too early in the Workflow, before the relevant data has come through.
My Condition Never Evaluates as True
If your True/False node stubbornly refuses to say “true,” it is worth checking:
- The condition is written the way you think it is, particularly when using greater-than or less-than logic.
- The value being tested is the type you expect, such as a number rather than text.
- The threshold or comparison value is realistic for the data coming through.
My Workflow Runs but Nothing Happens
If your Workflow appears to trigger, but nothing visible occurs at the other end, check:
- The nodes are all correctly connected. A missing or dropped link will bring things to a quiet halt.
- The final action node, such as email, SMS, or webhook, has been fully configured and not just added to the canvas.
- Any conditions along the way have not silently redirected the Workflow down the red-ball path instead of the green one.
Still Need Help?
Still stuck? Don’t worry. That is exactly what we are here for.
Contact our Support team, and we will help you get to the bottom of it.