Complexity Exhaustion when creating subitems via API

I am using make.com to create subitems in a monday board.
The query itself is fine and working.

In this specific scenario, I am listing items in a group (around 200 items) and creating a subitem for each item.

Each time, the 33rd operation fails, due to API cmplexity issues. It’s quite strange as I have done similar things in the past with no problem at all.

Here’s the error:

[200] [“Complexity budget exhausted, query cost 30001 budget remaining 9967 out of 1000000 reset in 0 seconds”] [ Error Code: complexityBudgetExhausted ]

Here’s the api call:

mutation {
create_subitem(
parent_item_id: {{7.id}}
item_name: “test”
column_values: “{"text": "0db9d56361", "email": {"email":"{{7.mappable_column_values.email.email}}","text":"{{7.mappable_column_values.email.text}}"}}”
) {
id
}
}

Does anyone no what might be the issue?

Thank you in advance!

Hello there @Flow and welcome to the community!

I hope you like it here :muscle:

It looks like you are hitting the rate limits as explained here.

If you are using Make.com, the easiest way to avoid it would be to just set a timeout (a block that “waits” for a few seconds) between each query. You can find other possible solutions in the link above :smile:

Cheers,
Matias

Hi @Matias.Monday, Thank you for the answer.

As the error is quite clear, the odd part, is that it happens after creating only 32 subitems. Why is this? I ran similar queries in the past and they all worked fine.

Looking forward to hearing from you

Hello again @Flow,

Matias here!

This will depend on how many points each of the mutations take, and also if you are using the API for any other operations. It looks like the amount of queries/mutations you are using multiplied by each operation’s complexity points usage, adds up to the limit. The number of queries/mutations itself is not relevant here, but the addition of points used is :smile:

Well that does make sense. But I am simply creating some sub items with just two columns. Anyhow, I will try to set the timeout. Thanks for the help!

Happy to help @Flow ! If you try this and/but believe there is an issue with the complexity points mechanism, please let us know here!