Our app edits orders by calling orderEditBegin, then sends several orderEditSetQuantity and orderEditAddVariant mutations concurrently against the same CalculatedOrder, then orderEditCommit (Admin GraphQL 2025-01).
Since roughly 2026-09-23 to 09-27, when an edit has more than about 30 changes, some of them return HTTP 200 with:
userErrors: [{ field: ["id"], message: "Another staff member may be editing this order. Try again." }]
No one else is editing the order. The rejections all arrive together, about 10 seconds after the requests were sent, and the requests that complete do so one at a time, about 0.35–0.4s apart. It looks like mutations on a calculated order are serialized, and a request still waiting after about 10s is rejected.
Questions:
- Was a change made to how concurrent order-edit mutations are handled (a lock or wait timeout) in late September 2026?
- Is the ~10s wait limit documented, and is it a fixed value?
- Is sending the changes as aliased mutations in a single request, one request at a time, the recommended pattern? That works for us with no rejections.