Skip to main content
Derek Junkin
Starter ⭐
Jun 19, 2026 2:10 PM UTC
Solved

Simultaneous Automated Actions - Conflict/Failure

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 LamAnswer
Explorer ⭐
Jun 20, 2026 11:58 PM UTC

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:

  1. If the second automated action is a webhook. Maybe you can trigger this second action in the last step in the first automated action.
     
  2. 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
 

Yush Lam

3 replies

Yush LamAnswer
Explorer ⭐
Jun 20, 2026 11:58 PM UTC

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:

  1. If the second automated action is a webhook. Maybe you can trigger this second action in the last step in the first automated action.
     
  2. 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
 

Translate
Yush Lam
Derek Junkin
Starter ⭐
Jun 23, 2026 7:05 PM UTC

Thanks, 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. 

Translate
Theo Hollenberg
Explorer ⭐⭐
Jun 28, 2026 3:35 PM UTC

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).

Translate
Enablement is key