Hi, the same thing happened with board column IDs. Subitem column in any board used to have an ID of âsubitemsâ but now when we add the first subitem to a board the column is created with an ID of âsubitems__1â. That change broke some of our appâs functionalities and similarly we donât recall seeing any announcement - did we miss something?
Guys, why are you making changes to the API for all versions?
We adapted our code for this error in the âcomplexityBudgetExhaustedâ format, we are using api version â2024-01â and suddenly the api starts working differently?
Currently our application on production does not work correctly due to this change.
@Nix0id â really apologize for this change, sending complexityBudgetExhausted was a bug on our side that we then fixed. It took a few days because we deployed less during the holidays.
Again, Iâm really sorry to hear that you updated your app to account for this bug, only for it to break again.
Iâve read about the change and rollback mentioned here. Iâd like to ask whether the rollback has been applied to all API users, as even after moving up to API version 2024-07 I am seeing the same error message format as pre-rollout
"errors":["Complexity budget exhausted, query cost 30001 budget remaining 9667 out of 10000000 reset in 58 seconds"],
"error_code":"ComplexityException",
"status_code":429,
"account_id":5493834}
This error was seen on May 8 US time. Function operates in an Australian cloud service.
We use the error_message field in the error response to automate a backoff-wait process and a reversion to the initial state (error_message field) would be good for us. While mentioning this, having a list of errors where the list is of variable length complicates the process, adding uncertainty.
Please advise on the future state of the error message so we can adapt to the API behaviour.