Item link max locks exceeded

Hello there @roundlab and welcome to the community!

I hope you like it here 💪

Would you be able to provide a full query with actual column_values so we can take a look?

We do not need the item or board ID, but the column_value’s object.

Cheers,
Matias

Thank you very much for your response,

The full request is like this (added the "" by the PHP function json_encode):
mutation {
change_multiple_column_values (item_id: XXXXX, board_id: YYYYY, column_values: “{"lieu":{"lat":"31.6374766","lng":"-8.012211299999999","address":"75 Rue Ibn A\\u00efcha, Marrakech, Maroc"},"texte36":"","texte3":"MA","texte45":"FR","lieu9":{"lat":"48.8675651","lng":"2.3458789","address":"95 Rue R\\u00e9aumur, Paris, France"},"texte02":" (Transport Routier)","chiffres26":0,"chiffres":1,"chiffres1":1200,"chiffres2":479.51999999999998,"chiffres14":1200,"texte60":"Qt\\u00e9 1 Euro Palette | Dimensions : 120 x 80 x 150(cm)\\n","texte7":"","texte6":"","texte1":"Mme wxdvwxcvxcvwxcv","e_mail":{"email":"sdfg@fg.com","text":"sdfg@fg.com"},"t_l_phone1":"+21265464564645","date":"2022-11-30","chiffres040":0,"chiffres47":2977,"chiffres21":1.4399999999999999,"chiffres147":952.69000000000005,"chiffres94":0,"chiffres6":157.69,"chiffres4":0,"chiffres9":90,"chiffres71":540,"chiffres0":0.45000000000000001,"chiffres37":138,"chiffres7":0,"chiffres72":27,"texte4":"sdgfgh","e_mail_1":{"email":"dg@.cl","text":"dg@.cl"},"t_l_phone9":"+2126549876541","texte44":""}”) {
id
}
}

regards,

Hello again @roundlab!

I was informed by our team that a fix was deployed regarding this issue.

Would you please confirm if the issue still persists for you?

Hello,

I hope you are doing well. I wanted to inform you that the issue you previously mentioned still persists. Currently, I am working on a project for one of our clients, which I started right after the API update on October 1, 2023. This update proved to be essential due to the introduction of filters that have proven to be extremely useful for many projects.

My work is carried out using the N8N tool. It involves retrieving all the items related to a supplier. However, two issues remain. Firstly, the retrieval of items is limited to 25, whereas there are 33 items to be retrieved. Secondly, the 25 items that are retrieved are converted into sub-items, but only 21, sometimes 22, are processed correctly. Starting from the 22nd item, an error message appears, stating: “error_code: ColumnValueException, status code: 200, error_message: Item link max locks exceeded, error_data: [empty object], data: [undefined].”

I would like to express my gratitude in advance for your assistance and guidance in resolving these issues.

Best regards,

Delépine Tom

The 25 item limit is set with the limit argument in the items_page and items_page_by_column_values up to 100 as noted in the documentation for items_page.

What do you mean by converted to subitems? I am not aware of any API mutation that can convert an item into a subitem like can be done from the UI.

Thank you @anon29275264 !!

The 25 limit information is correct. You can pass a higher limit for it.

Regarding the second issue, I will need you to please send over an email to appsupport@monday.com with all the relevant information so we can take a look into it.

Please include the exact mutations you are using, the response you are getting and if you can, a timestamp of the last time this happened (you can test it now and write down the data if you want) including date, hour, minute, board ID and your user ID.

Looking forward to hearing from you via email!

Cheers,
Matias

Hello,

I apologize for the confusion in my choice of words. It’s not really about “converting,” but rather “creating” one or more sub-items that retrieve all the information from their counterparts in the database. Thank you very much for your assistance. Indeed, I had not specified the limit parameter, thinking it would retrieve all items if I didn’t set a limit. So, I have now configured the limit to 100.

Best regards,
Tom DELEPINE

Thank you @anon29275264 for the information provided here!

I don’t know how N8N works, does it create the subitems in parallel or iterate the array and create them one at a time?

Ensure its iterating. As silly as is it sounds (and unideal) as a workaround you could add a 50-100ms delay between each iteration. I know this doesn’t solve the issue, but at the very least it lets you get something deployable (which seems to be most important!)

Hello,

Indeed, N8N processes each of these items individually, one by one, following the top-down order and using their JSON format. Although the idea of adding a delay may seem promising, I observed through tests that the error can occur as early as during the processing of the first item. After that, the process may continue as if nothing happened, and errors can randomly manifest themselves later on.

In any case, at the end of the process, the number of sub-items created never exceeds 20 or 21, even when a higher number of items is retrieved, whether it’s 22 items or 33 items.

Thank you for your attention to this matter.

Best regards, Tom Delépine

Hello,
I apologize for my delay. I ultimately resolved the issue in a different way because I couldn’t find a solution. There was an option to manage the time spent in the node, but it didn’t work as I had hoped. So, I decided to limit the number of items retrieved with a filter to 21, and then I used the “cursor” from “next_item_page” to process multiple sets of 21, all while checking if the “cursor” stat was empty to determine if I had reached the end of the item set.