If you set up multiple automations with steps that compete with each other, you may run into unexpected behaviors, errors and failed automation runs. 

In this article, we'll guide you about what it means to create competing automations, how you can solve the issue, and how to avoid running into it in the future.

What are competing automations?

Competing automations refer to automations that have the same trigger (or also one automation with multiple actions) where the actions run at the same time and will conflict with each other. 

For example, let's say we set up the following two automations on the same board:

1When status changes to something, archive the item.

2When status changes to something, change another status to something.

Because these automations start with the same trigger, "When status changes to something", both of them will run at the same time.

These automations will fail because the automation changing the item's status to "Working on it" will not be able to run due to the fact that the other automation caused that same item to be archived.

Triggering competing automations

Let's continue with the two automation automations shown in the example above.

If you trigger these automations multiple times by changing the Step 1 status to "Done", some of the automations will work properly, while others will not.

When this happens, you'll also receive a notification telling you that your automation has failed:

If you look at Automation run history you will see the list of all automation runs, including both the successful runs and the failed ones. You can also see the specific automation Run history by clicking on the notification shown above.

There you can click on the failed run, which will open up an explanation outlined in red that will expand more about why the automation failed.

In this particular case, it was due to having an archived item on the board:

Examples of competing automations

While there can be different scenarios that lead to competing automations, the main ones involve any "final stage" automation actions that either move an item to another board, archive an item, or fully delete an item. 

Here are three different examples where automations will compete with each other and will lead to some of them failing to run:

Example 1: One automation moves an item to another board

Example 2: One automation archives an item

Example 3: One automation fully deletes an item

How to solve the issue

To solve the issue of competing automations, start by deleting the separate automations that are competing with each other.

Next, build one single custom automation that accomplishes both actions instead.

For example, the two following automations:

1. When status changes to something, archive item
2. When status changes to something, change another status to something

Can be combined into one custom automation:

• When status changes to something, then set status to something, and then archive item

Note: Make sure to add any "final stage" actions (move item to board, archive item, or delete item) as the last step of the custom automation.