I used a temporary automation to add a Done label to all existing cards in my Done list before archiving them, so they would remain identifiable in Trello’s general archive.
I then used Trello’s native Move all cards in this list command once.
That single bulk action caused the automation to fire once per card and consumed my entire 250-run monthly Free allowance:
- Runs: 250 / 250
- Operations: 250 / 2500
I understand that the rule technically triggers on each card, but from a user perspective this was one bulk operation, not 250 separate automation actions initiated by me.
This seems like the wrong way to account for automation usage. A native bulk command should ideally count as one automation run, with the individual card changes counted as operations.
Is this expected behaviour, and is there any way to perform a bulk automation like this without exhausting the monthly run allowance?
Hello @boardtc
Trello defines an automation run as every time an automation is triggered. Although Move all cards in this list is one bulk action from the UI, each card is still moved individually from the Automation rule's perspective.
Here some overview from Documentation Automation quotas and limits | Trello | Atlassian Support
Automation overview | Trello | Atlassian Support
Best,
Arek🤠
That page says "Automation run: Every time an automation button is pressed, or an automation is triggered, it counts as one automation run."
It's not clear and open to interpretation.
Anyway, I need to wait until Tuesday.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Arek's answer is right, and the reason that sentence reads ambiguously is that the counter is on triggers rather than on clicks. Your rule's trigger is a per-card condition, so one press of Move all cards in this list generated 250 separate trigger events.
Your own log settles it. Runs 250 of 250, operations 250 of 2500. That is one operation per run, which is a single label action fired 250 times. Had one run swept the whole list you would be looking at 1 run and 250 operations.
The docs do separate the two ideas, though not in the sentence you quoted. A board button is described as one that reorders or moves all cards in a list matching specific criteria, and there is a distinct limit named the number of cards a single automation run will affect, which only means something if one run can touch many cards.
So the shape that costs you one run is a board button doing the bulk work, not a rule each card trips on its way past.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.