Troubleshooting Flows: Common Issues and Solutions Overview

Most problems with Zoho Flow fall into a few common categories: creating or saving a flow, a flow failing during execution, or managing your organisation and users. This guide covers the usual causes and simple checks to resolve them.

Issues creating or saving flows

• If a connection will not create, disable browser extensions that may be blocking it and try again.
• If a newly added field in a connected app is not showing up, open the action, click the edit icon, and click Done again to refresh the available fields.

Flows failing during execution

• Check that mandatory fields have valid values, dates and times are in the correct format, and no character limits are exceeded.
• Check whether a field was removed or changed in the connected app since the flow was built.
• Confirm your Zoho Flow plan supports the trigger or action you are using.
• Check whether you have used up your monthly task allowance.
• Remember that third-party apps can apply their own API rate limits, which may need their support team to resolve.

Why a flow switches off automatically

Zoho Flow automatically turns a flow off after 20 consecutive failed executions, or if the trigger’s authentication fails because a connected user account or authorisation token has been revoked. Reconnect the affected connection and switch the flow back on once the issue is fixed.

Duplicate records or high task usage

Unexpectedly high task usage or duplicate records are often caused by flows triggering each other in a loop. Review how your flows are connected and, where an action might fail, add an error branch (On Error) so the flow follows an alternative path instead of stopping.

Platform and organisation issues

• If a connected app is restricting access, you may need to allowlist Zoho Flow’s IP addresses.
• A flow deleted by mistake can be restored within 90 days from the Audit Trail.
• An inactive organisation can be reclaimed by an admin using the Claim Ownership option in Manage Organizations.

Tips

• Check the History tab first for any failing flow: it shows the exact step and error.
• Use error branches to keep flows stable when an occasional failure is expected.
• Watch for sudden spikes in task usage, which often point to a looped trigger.