Why is my Zoho CRM workflow not triggering?
When a Zoho CRM workflow does not trigger, the fault is almost never the platform - it’s configuration. The nine causes below cover nearly every broken automation we’re asked to fix, listed roughly in the order worth checking. Most take minutes to resolve once identified.
Before you start, pin down one distinction: is the workflow genuinely not running, or is it running while its action fails? A workflow that sends no email looks identical to one that never fired and the two have completely different fixes. Cause 8 shows you how to tell them apart.
1. The rule criteria do not match the record
The most common cause is also the simplest: the record you’re testing doesn’t actually meet the rule’s criteria. Open the workflow, read the criteria line by line, then open the record and compare it field by field. Watch for these traps:
- Picklist values that look right but are not exact. Criteria match the stored value, so a renamed picklist option or a stray trailing space is enough to stop the rule matching, with no error to show for it.
- AND where you meant OR. A rule requiring Lead Source equals Web and Industry equals Finance fires far less often than one requiring either.
- Criteria built against the wrong layout. In multi-layout modules, a rule can be scoped to a layout your test record does not use.
The reliable fix: strip the criteria back to a single condition you can guarantee, confirm the rule fires, then reintroduce conditions one at a time until you find the one that breaks it.
2. The execution event is wrong: create vs edit
Every workflow rule is bound to an execution event - typically Create, Edit, Create or Edit, or a specific field update. If the event doesn’t match how the record changed, the rule never evaluates at all, no matter how perfect the criteria are.
The classic mismatches:
- The rule is set to Create, but your records arrive as updates from an integration or a sync tool.
- The rule is set to Edit and you expect it to fire on brand-new records. It won’t.
- The rule fires on edit, but the option to repeat the workflow whenever the record is edited is unticked - so it runs once per record and never again, even when the criteria match later.
- The rule watches a specific field for changes and your process updates a different field.
Fix: open the rule, check the execution event against the real-world path the record takes and switch to Create or Edit if records can arrive either way.
3. Workflow order and conflicting rules
Multiple rules on the same module can all fire for the same save and they don’t always cooperate. Two rules updating the same field will fight and the visible result depends on which finishes last - which looks exactly like one rule “not triggering”.
There is also a deliberate platform behaviour that catches almost everyone: a field update performed by a workflow does not trigger other workflow rules. Zoho CRM does this to prevent infinite loops. If Rule A updates a field and you expect Rule B to react to that change, Rule B will sit there doing nothing. Restructure so a single rule carries both actions, or move the chained logic into a custom function, which can update records in a way that does re-evaluate rules.
4. Conditions failing on blank fields
Criteria are evaluated at the moment the record is saved, so a condition on a field that’s empty at save time can’t match - even if the field is filled in seconds later by another automation or by a user finishing the form in a second pass.
This bites hardest in lead capture: web forms and integrations often create the record first and enrich it afterwards. If your rule fires on Create but the qualifying field arrives in a later update, combine the fix from cause 2 (use Create or Edit) with criteria that tolerate the field being populated late. Where a value is genuinely essential, consider making the field mandatory on the layout so records can’t be saved without it.
5. The rule is inactive
Obvious and still one of the most frequent findings. Rules get switched off during testing, sandbox deployments or troubleshooting sessions and never switched back on. Go to Setup → Automation → Workflow Rules and check the status toggle - and while you’re there, check the audit log to see whether anyone has edited the rule recently.
6. Imported and API-created records may skip workflows
How a record enters CRM matters. Records created through Zoho’s data migration tool skip workflows entirely - by design, so a historical import does not fire thousands of emails. Records held for manual approval after an import do not trigger rules until someone approves them. And records written through the API can have workflow execution suppressed by the calling application: the API exposes a trigger parameter and plenty of integration and sync tools disable workflows deliberately.
If your rules work for hand-entered records but not for records arriving from a form, a sync or a third-party app, start here. The fix usually sits in the integration’s configuration - something we deal with constantly in our Zoho integrations work.
7. A Deluge custom function is failing silently
If the workflow’s action is a Deluge custom function, the rule can trigger perfectly while the function dies at runtime - and nothing obvious appears in the interface. Common culprits include null values the script does not handle, API call limits, expired connections to third-party services and record IDs that do not resolve.
Three things to check:
- Failure notifications. Zoho emails the function’s author when a function fails - search that inbox before assuming the workflow never ran.
- Run the function manually against the same record ID and read the error it returns.
- Add info statements at key points in the script so the execution log shows how far it got.
Fragile Deluge is one of the most common things we untangle in Zoho CRM projects - functions written years ago that fall over the moment a field is blank.
8. The workflow fired - but the email never arrived
A remarkable share of “workflow not triggering” reports turn out to be email deliverability. The rule evaluated, the action ran and the message bounced, landed in spam, or was rejected by the recipient’s server.
Check the record’s email related list: if the workflow email shows as sent, the workflow is fine and the problem is deliverability. Verify your sending domain’s SPF and DKIM records, check bounce reports and confirm you haven’t exhausted the daily cap on workflow emails for your edition. If the email is not listed at all, the workflow genuinely did not run - go back to causes 1 to 7.
9. You have hit a workflow limit
Every Zoho CRM edition caps the number of workflow rules per module, workflow emails per day and custom function executions. The frustrating part is that hitting a cap rarely produces a visible error - actions simply stop happening, often partway through a busy day, then mysteriously resume the next morning.
If automations work in the morning and fail in the afternoon, suspect a daily cap. Audit your active rules, deactivate redundant ones, consolidate overlapping rules into fewer, better-structured ones and if you’re genuinely outgrowing your edition, weigh up an upgrade against tidier automation design.
Quick diagnostic checklist
Run through this in order - it isolates the cause in a few minutes:
- Is the rule active?
- Does the execution event (create / edit / field update) match how the record changed?
- Create a fresh test record that meets the criteria exactly. Does the rule fire?
- Strip criteria to one guaranteed condition, then add conditions back one at a time.
- Did the record arrive via import, migration or API? Check whether workflows were suppressed at the source.
- If the action is a custom function, run it manually and check failure notification emails.
- If the action is an email, check the record’s email list and your domain’s SPF/DKIM before blaming the workflow.
- Did automations stop partway through the day? Check edition limits and daily caps.
- Is another rule or a Blueprint interfering with the same records?
Still stuck? Get a senior developer on it within 30 minutes
If you’ve worked through the list and the workflow still refuses to fire, the cause is usually buried deeper - a Blueprint restricting records mid-process, an integration suppressing triggers at the source, or a Deluge function failing only on certain data. That’s what our emergency Zoho developer service is for, with the 30-minute response from a senior developer. For the longer game, our Zoho support plans keep automations maintained so problems are caught before anything breaks.
Talk to us
H4Z is a UK-based Zoho consultancy working across the entire Zoho suite for clients worldwide. If a broken workflow is costing you leads or hours, get in touch: the discovery call is free and we’ll tell you what’s wrong and what the fix involves.