generic.Error.CONCURRENT_ITEM_UPDATE

Hello!

Our content team has been facing recently the following error when editing a page or blogpost:

Bildschirmfoto 2025-05-15 um 08.41.25

What could be causing this? It is an annoying issue that affects our content team negatively so it would be appreciated to track down the root cause of it :slight_smile:

Many Thanks!

Hi @technology!

That error happens when two API requests are racing each other and making conflicting updates: CMA Error Codes (REST) | Documentation โ€” DatoCMS

CONCURRENT_ITEM_UPDATE

This error occurs when an attempt is made to modify a record that is concurrently being updated by another API request. This typically happens when two API requests try to change the same record at the same time. To resolve this, ensure that you implement retry logic in your application, allowing it to gracefully handle such conflicts by retrying the request after a brief wait.

Are you perhaps running some API update scripts at the same time your editors are making changes in the UI? If so, the way around that is to use optimistic record locking with your API calls: Update a record โ€” Record โ€” Content Management API โ€” DatoCMS

If youโ€™re NOT making any API calls and this is happening with multiple editors just working in the UI at the same timeโ€ฆ I think that is a bug! Usually the UI will warn them that โ€œSoandso is also working on this record. Do you want to take over?โ€ Collaboration features | Documentation โ€” DatoCMS

If you are seeing a situation where that isnโ€™t happening, could you please give us more details (like a video recording, or details about what the different editors are doing)? It may be a bug, or a custom plugin youโ€™re using (if any).

1 Like

Thank you so much for the quick response :pray: :slight_smile:

We forwarded the possible causes to our content team and asked them to report if it occurs again.

1 Like