Order of Butler Actions

Question

I have a Trello board set up to manage our company workflow. The cards represent projects and the lists are steps in the workflow process. Each time a card is moved to the next step (list) someone new is responsible for the card and it receives a new deadline.

The way I have the Butler actions set up is when a card is moved out of a list it removes all members and due dates. When it moves into a list it adds members and sets a new due date based on the list it is moved into.

This works well most of the time but occaisionaly when a card is moved into a new list, the "add member" and "set due date" actions will run before the "remove members" and "remove due dates" action. So the members and due dates get added but are immediately removed from the card. This only happens on 2 of the lists and I cannot figure out why.

Any help would be appreciated.

Vongsawat · Answer

If your commands are too long, you can chain together multiple rules by using a number of labels to trigger them in order.

The first rule can trigger when something gets added to List A as normal. But the last action it does is add a label "processing_1".

The second rule then triggers when "processing_1" is added to a card. Perhaps only if its added in List A to ensure no accidental triggers.

With further rules and the last one clearing the triggers.

You can also maybe add a general "processing" label in the first rule, then have all secondary rules and beyond also only trigger if the card has the general "processing" label. That way someone would have to fuck up twice by applying both labels for it to trigger etc.

Hope it works out.

Bill Weaver_f2dt01 · Answer

While having 1 rule to do all would be easier and neater,  you also run the risk of exceeding the max number of commands per rule.  I believe that is 20 commands?   i run into this myself, and do something similar where a card is moved into the board, or to a new column on the board, activates adding checklists, assigning items to those checklists, adding calculated due dates for those items, based off a certain custom date field=, adding users, etc...   I had to break this down into several rules.  Sometimes it fires in the right order and works great, other times, the wrong rule is fired, then the next, all out of order.   I fully understand Eric's question.  I am going to try Vongswat's proposed solution to see if it works in my case.

Vongsawat · Answer

Esme's solution for a single rule that removes then adds is probably your best bet.

But if there is a reason you want to keep them separate (for instance some rules are doing additional list-specific actions). Then you could modify the rule triggers so that you never risk having them happen in the wrong sequence.

Add a specific label at the end of the Moved Out Of list X rule.

And change the trigger of Moved In To list Y, to trigger instead on when the specific label is added to a card in list Y.