Looping is a scenario in which a set of connected tasks execute repeatedly. When such loops are not regulated, they execute endlessly, creating infinite loops. A flow loop happens when a flow gets invoked repeatedly without any intended trigger events. A typical case is when two flows perform actions in such a way that they trigger each other. This can cause the flows to send the same data to and fro repeatedly, creating numerous duplicate entries in your connected apps. This also leads to exhaustion of your available tasks within a brief period.
Infinite flow loops may show some or all of these symptoms when the flow is switched on:
Looping can occur in different ways.
Suppose you want to sync newly created data between Zoho Projects and Trello. Every project created in Zoho Projects must have a corresponding board in Trello, and vice versa. However, when a board is created in Trello as a result of the first flow's action, it triggers the reverse flow automatically, creating a new project in Zoho Projects. This continues because the flow is set up to trigger on any newly created entry. The solution is to understand how your apps are connected, and to implement logical conditions in your flows that prevent duplication of data.
Step 1: Ensure that the trigger in one of the flows contains a field that you have control over. For example, you could create a custom field, say Status, a field that you can fill in with a keyword of your choice.
Step 2: Click Logic in the flow builder and drag the Decision block onto the builder between your trigger and action. Set the decision to run only if the custom field from step 1 contains your keyword. For example, you could configure your flow to run only if your keyword is entered in the custom field created (in this example, Status). Whenever you create a project, remember to use your keyword (for example, "key1").
Step 3: Set up the second flow.
Step 4: Whenever you create a project, make sure you include "key1" in the custom field in Zoho Projects. This avoids the exchange of duplicate entries between the connected applications.
Note: This method works by using a user-controlled field that indicates to the flow that the record creation was performed by a user, and not an automated duplicate entry. Remember to use a newly created custom field or typically unused fields, like Description or Notes, for keywords to keep the auto-generated or important fields like Title or Project ID undisturbed.
If you are using a fetch action to sync newly created records between two apps, add a Decision block that allows the flow to continue only if the fetched record values return null. This ensures that the second app does not hold similar data. Configure the second flow in the same way.
Suppose you have created a flow that takes in new tasks created in Asana and creates to-dos in Basecamp. There might be another flow that creates a new row in Zoho Sheet for every to-do created in Basecamp. Later on, a flow is created that syncs the task data between Zoho Sheet and Asana. This completes a loop, and there is no filter to stop the flows from executing repeatedly.
This happens when multiple flows connecting different apps form a chain that returns data to the initial app, resulting in a loop.
Identify all the flows that connect your apps. If there are flows that sync data, make sure that none of the actions in your flows trigger other flows. If such a connection is necessary, make sure to set Decision blocks to let the flows run only if the records do not match the original.
Suppose you have an already-existing custom function that syncs data from Zoho CRM to Zoho Books. If you create a flow that syncs data from Zoho Books to Zoho CRM using Zoho Flow, it can complete the loop and generate duplicate entries.
Identify already exiting connections between the apps. This includes direct integration using code, external data syncing applications and others.
Wherever you come across the symptoms that are usually associated with infinite looping, try to resolve the issues yourself by carrying out the following steps:
TURN OFF the concerned flows immediately
Immediately turn off all the flows that connect your concerned apps when you detect something is wrong with its records. Wait for a few minutes to see if the data duplication is still going on. If it's not, check if the scenario falls under the above-mentioned scenarios and try the solutions given.
Check your flow logs
Go to Settings and navigate to History to view your Task History. This gives you the status of how your flows are running, and lets you identify problems as soon as they occur. Click on a task to view the detailed log of that particular execution.
Check for other integrations or codes
If turning off the concerned flow does not stop the behavior, look for other integrations using code or other third party applications that connect your concerned apps.
If everything else fails to solve the issue, you can write to our support team at firstname.lastname@example.org
Learn how to use the best tools for sales force automation and better customer engagement from Zoho's implementation specialists.
If you'd like a personalized walk-through of our data preparation tool, please request a demo and we'll be happy to show you how to get the best out of Zoho DataPrep.
Write to us: email@example.com
Watch comprehensive videos on features and other important topics that will help you master Zoho CRM.
Download free eBooks and access a range of topics to get deeper insight on successfully using Zoho CRM.
Sign up for our webinars and learn the Zoho CRM basics, from customization to sales force automation and more.
Make the most of Zoho CRM with these useful tips.