Simultaneous Automated Actions - Conflict/Failure

Question

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?

Yush Lam · Accepted Answer

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?

Best answer by Yush Lam

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 in 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

Theo Hollenberg · Answer

You could make 2 webhooks and let the first process start the second. Than it's consecutive. But this is only if you want to keep the functionality of both webhooks separate (i.e. separation of concerns).

Sign up

Login with your MyTOPdesk account

Login to the community

Login with your MyTOPdesk account