Service Catalog Flow Re-triggered from second Flow calling the "Ask for Approval" Action.

[Mark Brogna]

I have created a Flow that creates one to many RITMs based on selected records in a catalog item’s list collector variable.  The reason I want RITMs is to have each RITM operate independently as it navigates its way through approvals and task assignments.  The first flow has a trigger of Service Catalog, where I clone the existing RITM for every item identified by the list collector.  Further, I create a related link between the RITM and a record in the custom table referenced in the list collector. Once these new RITMs are created, I set the original RITM to a state of “Complete Skipped.”

Example: from the catalog item, I select two Site records from a custom table:

Here is my Flow:

You will note this flow operating independently and correctly creates two RITMs and closed the original.

My Second Flow is designed for each RITM to go through its own unique instance of flow. This second flow has a trigger that starts when any record is created in the M2M table, relating the RITM to the Custom table record. However, if the first action is an “Ask for Approval” it seems to re-trigger the initial flow, thus creating more RITMs.

Once activated this is how my flow reacts by creating additional RITMs by triggering the initial flow.

Does anyone know how to stop this from happening?

[Mark Brogna]

Is there way to identify the original RITM created other than performing a count?

[Swapna Abburi · Accepted solution]

As you are adding RITMs to M2M table, you can use lookup records action to verify if current RITM present in M2M table. if it exists, you can skip the remaining steps in your first flow.