Hi Team,
I have a flow which runs on Incident form during update if Caused by change is not null or changes.
If it matches the condition then a change task is created for caused by change. I have added a checks to see if that particular task exists then do not create a change task.
But the issue here is, when user tries to add caused by change for multple incidents at a time - Let say adding 5 incidents here. That means caused by change for 5 incident gets updated and flow gets executed 5 times which is right. But since all 5 flows are executing at the same time, system is creating 5 tasks instead of just 1 task.
Has anybody seen this kind of scenario? Any alternative approach you can suggest or fix for this issue?
Hi @SM16 ,
Can you explain more on the assiciation of inc > change and > change task.
Is it parent child inc ?
☑️ Please mark responses as HELPFUL or ACCEPT SOLUTION to assist future users in finding the right solution....
Hi Khilji,
Incident and Change requests can be associated with each other in multiple ways. When change is associated with an incident, I am checking if task is created then do not create otherwise create a task.
1) 1 to 1: Where you open an incident and there will be a reference field for the change request to create 1 to 1 relationship (Only 1 flow is triggered here since only 1 incident is updated)
2) Many to 1: Here you go to the change request related list where you have M2M table to relate multiple incidents to single change (Here multiple incidents gets updated with same change and triggers multiple flows)
When an incident is updated with change request fields reference, I am triggering the flow. But when user relates multiple incidents at once, all flows are getting triggered and causing my if condition failure.
Technically, 5 flows should be triggered since I have them written on incident updated but with user action, all incidents are getting updated simultaneously and flows are also executing simultaneously, the system cannot check if the task is created.
