Help for owners
My Zoho Flow automations keep failing or stopping
Short answer
Zoho Flow keeps a history of every flow run, so the first step is to open it and read the error on the failed run. Zoho lists the usual causes: a connection that needs authorising again, an app that blocks Zoho's IP addresses, a flow that triggers itself, and errors from the connected app.
Does this sound like your situation?
- A flow that worked for weeks now shows failed runs.
- Orders, leads or invoices are not being passed between my apps any more.
- One flow seems to run again and again.
- I clicked Authorize and nothing happened.
- I am not sure if a plan limit or an error stopped it.
Why does this happen?
A connection needs authorising again
Each app in a flow uses a connection to your account in that app. When the login behind it changes or is revoked, the flow fails until the connection is authorised again. Zoho notes that if clicking Authorize does nothing, a browser pop-up blocker may be stopping the authorisation window.
Confirmed by help.zoho.com
The connected app returns an error
A flow only passes data between apps. When the other app rejects a record, for example a required field is empty or a value no longer exists, the run fails at that step. Zoho describes automatic and manual reruns of failed executions, and says automatic rerun covers failures from Zoho Flow's internal errors or API errors from the connected app.
Confirmed by help.zoho.com
The other app blocks Zoho's addresses
Zoho states that if your apps restrict access, you must allowlist Zoho Flow's IP addresses so data can be exchanged. A new firewall rule or security setting can silently cut a flow off.
Confirmed by help.zoho.com
A flow triggers itself
Zoho explains that infinite looping occurs when a flow is repeatedly invoked by its own actions, for example a flow that updates a record which in turn starts the same flow.
Confirmed by help.zoho.com
The plan's usage allowance
Zoho's subscription documentation covers flow limits, what counts as a task and when the task count resets. Which limit applies depends on your Zoho plan, so check the usage page of your own account before assuming an error.
Confirmed by help.zoho.com
What can I do about it today?
- Open the execution historyZoho states that it lets you access the history of all flow executions in your organization. Find the first failed run and copy its error message.
- Check whether one step or all steps failA single failing step points to that app or that record. Every run failing points to the connection or the trigger.
- Authorise the connection again if it asksIf the error mentions authorisation, re-authorise from the connection, and allow pop-ups for the Zoho page first.
- Do not switch off other flows to testLeave the working flows as they are. Turning flows off and on can create missed or doubled records.
- Send the notes to the person who built the flowGive them the flow name, the first failure time, the error text and what changed in either app just before.
When should I bring someone in?
- The same flow fails again after you authorise it.
- Records are missing or doubled in the connected apps.
- The flow you need is more than Zoho Flow's steps can express and has grown hard to follow.
How do I handle it?
- Read the run, not the guessI start from the execution history: the first failure, the step, the record and the message. I also read the vendor's current documentation before changing anything.
- Check what changed on both sidesI compare the failure time with changes in either app: permissions, required fields, firewall rules, a user who left.
- Repair on a copy firstI test the fixed flow with sample records before it touches your live data, and look for loops and missing guards.
- Catch up the missed recordsI list the records that did not pass through while it was failing and send them once, checking for doubles.
- Move heavy logic out if it outgrew the toolWhen one flow has become a long chain of conditions, I describe what a small code-based service would do instead, so you can decide.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
Can a failed run be run again?
Zoho documents reruns of failed executions, including an automatic rerun for failures from Zoho Flow's internal errors or API errors from connected apps. Check the record afterwards so it is not created twice.
How do I know if it is a plan limit?
Zoho's subscription documentation covers flow limits and what counts as a task. Read your own account's usage page and compare it with the time of the first failure.
Why does a flow run over and over?
Zoho describes this as a loop: the flow's own action starts the same flow again. It is fixed by changing the trigger or adding a condition that stops it.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.