Is that really bad?
I have a scenario that causes Convex to raise the following error frequently, but this is sort of expected. I mean, we do have concurrent stuff running, but they are designed to be tolerant.
Is it too bad to let it live like that? Or I should be worried and look for a fix?
Documents read from or written to the "actions" table changed while this mutation was being run and on every subsequent retry. A call to "action/lifecycle/private.js:_resolve" changed the document with ID [...]3 Replies
up
OCC errors - maybe Workpool component can help? https://www.convex.dev/components/workpool#optimize-occ-errors
Convex
Workpool
Workpools give critical tasks priority by organizing async operations into separate, customizable queues.
i'll check it out, thx!