We have an event that triggers two separate automated actions to update an incident. Is there the chance of conflict/failure with this set-up?
For example, the first task is updating an incident and the second fails to update because the first is in the process of updating. Is this a concern?
Question
Simultaneous Automated Actions - Conflict/Failure
+2
We have an event that triggers two separate automated actions to update an incident. Is there the chance of conflict/failure with this set-up?
For example, the first task is updating an incident and the second fails to update because the first is in the process of updating. Is this a concern?
Hi Derek Junkin,
If you have one trigger that execute two sperate automated actions to update the same incident. Then yes, you may potentially get this conflict, because the trigger triggers on the same moment.
My idea will be: Somehow you have to create a slight delay between the two actions. And this depends how the automated actions are made. There are few idea's/examples, such as:
- If the second automated action is a webhook. Maybe you can trigger this second action in the last step in the first automated action.
- Or if possible, maybe you can create two triggers based on time action. One with 0 minutes delay, second with 1 minute after.
I hope this will help.
Kind regards,
Yush Lam
+2Thanks, Yush. We haven’t seen it fail, yet, but figure it’s likely possible as you say.
We may space this out to occur a minute apart or combine the automated actions into one.
Login to the community
No account yet? Create an account
Login with your MyTOPdesk account
Log inor
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.