PTaking latest timestamp for duplicates
For a specific conversation, our app fetches messages from an external service and stores them in our convex
As we're running through this workflow for 1000s of messages, we split them and call our storage mutation for each batch of messages. We also use the scheduler to run this message fetching for multiple conversations.
Since we're reading and mutation the same fields, this raised the following error:
As @presley mentioned, we should either delay each scheduled fetching/storage flow, or ensure we aren't mutating/reading the same fields across scheduled actions.
Not querying the table before storage and just inserting the
Which solution approaches are recommended for this kind of workflow?
messagesmessagesuserIdmessageIdpatch()insert()As we're running through this workflow for 1000s of messages, we split them and call our storage mutation for each batch of messages. We also use the scheduler to run this message fetching for multiple conversations.
Since we're reading and mutation the same fields, this raised the following error:
OptimisticConcurrencyControlFailure: Data read or written in this mutation changed while it was being run. Consider reducing the amount of data read by using indexed queries with selective index range expressions (https://docs.convex.dev/database/indexes/).As @presley mentioned, we should either delay each scheduled fetching/storage flow, or ensure we aren't mutating/reading the same fields across scheduled actions.
Not querying the table before storage and just inserting the
userIdmessageIduserId, messageId, convoIdWhich solution approaches are recommended for this kind of workflow?
