Not the best solution, but every additional user is an additional 200 command runs in the pooled command quota, so one way may be to buy additional dummy seats?
The better option is probably just aggressively streamlining Butler to use as little rules as possible, and just go ham on operations per rule instead for instance.
If you have a rule triggering 20 times a day, whose minor update is necessary but maybe not immediately. Maybe think of making a Card Button instead, that filters for all the un-updated cards, puts them in to a TempList as links, then acts on each of them in bulk, before deleting the TempList. Maybe splurge with 2 command runs and have that trigger on a Scheduled Rule at the end of every day. etc. Or replace the Scheduled Rule with a non-Butler Repeating Card power-up.
Probably not the answer you're looking for. But hope that helps.
@Robert Farnsworth Command quotas and, for that matter, API Rate Limits are real challengers for Trello users especially when deployed in an enterprise setting. IMO the command quota is just a higher level abstraction of the API rate limits https://help.trello.com/article/838-api-rate-limits and the recommendation there is to use webhooks.
The platform that I am using for most of my investigation is Wayscript which already has a set of triggers and modules. The means that you can use them to overcome the quotas. However, it does mean more effort to decide what to offload to this approach and the development and testing required before deployment. One very trivial limitation I found for me what that the triggers requires a user account to that these modules and triggers can be set to specific boards, list or cards.
@Vongsawat have probably heard me advocate for Butler. IMO the bigger issue is the cost of doing business when quotas have been exceeded.
I have a series of investigations done which I have created videos. See my profile re website (yes, just a link to youtube playlist). The latest few goes further to investigate on Power Ups and dashboard. Now I am studying on how webhooks can be used to complement my Power Up and Dashboard to mitigate risk of hitting rate limits.
My apologies for a long answer to your question. There is a solution out there that works best for you and your enterprise.
I am not as familiar with Butler as much I should.
I just came across http request when reading a reply on quotas. Why it excites me?
Recently, I created Superhero Power where registered users can execute pre-tested modules in a Sandbox. It has moved from there to a concept, I called Superhero Basecamp, where the user brings the app in house and execute the code from a board via custom Card button through an endpoint in Superhero Power.
I would imagine you can offload most of the routine processing that way to an endpoint while staying within the rate limits. There is probably no limits on what one can do once the endpoint receives the data....e.g. setup a webhook that will monitors all actions ...do something about them and remove the webhook, or use existing webhook but activate work based on the specific requirements submitted at the endpoint to customise the behaviours etc end of day/week/month processing
Above is conceptual at this moment as I have not tested it. Might just do one today.
Hello Community! My name is Brittany Joiner and I am a Trello enthusiast and Atlassian Community Leader. I'll be sharing with you a series of videos with my top tips on how to best use Trello...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events