Thank you for the continued dialog @Helen, @dipro.
There are several issues with this change, but for the purpose of this conversation we will ignore the fact that there was no notice to this change, and that this change fundamentally changed contractual terms.
The primary driver as to why we are exhausting this new budget has nothing to do with overly complex queries, but the simple fact you charge a minimum 100,000 units for a ‘items_by_column_values’ query.
Since Monday is missing several key pieces of functionality, such as cross-board rollups, or the ability to lookup a value from another table (VLOOKUP), we have had to implement these features ourselves through custom integrations. By their nature, these automations rely on finding the appropriate items within a Monday board where we don’t know the item’s ID. Thus the use of the ‘items_by_column_values’ query. You then multiply this by the fact that there are hundreds of items being manipulated by our various teams each minute, this adds up.
Hope this helps explain that this problem can’t go away by simply writing more “efficient” queries as your team postulates, but is rooted in the fact there is a significant tax placed on areas of the API that are critical for integrations to actually use Monday as a WorkOS.
I’ve attached a screenshot of the impact this is having on my business. This is one of our automations in Integromat showing all the jobs that failed due to the query limit being exhausted. These jobs are now all queued up to try again. The problem is that people are still working, so once more budget frees up, it’s a race to use that budget by some of these queued jobs, but also new ones coming in from people doing current work. This is a thundering herd problem that doesn’t resolve itself until rate frees up as people stop doing work, or the retry attempts finally fail and the job fails completely.