Error: Completing draft orders via GraphQL (draftOrderComplete, API version 2022-04) intermittently fails with the message “Resulting order was not persisted.” The mutation converts a draft order into a finalized order.
Observed behavior: The error appears sporadically; retrying the same call sometimes succeeds. Reports suggest this started in recent weeks. One participant also cannot create orders from the admin dashboard (screenshot provided), indicating impact beyond API calls.
Workarounds/ideas: Retrying is the only consistently reported workaround. Some consider upgrading to a newer API version, but there is no confirmation it resolves the issue.
Impact: Blocks automation and manual order creation for some users, with potential revenue loss.
Official guidance: A staff member states the error is generic and can be caused by multiple issues. They request specific, reproducible examples (steps and Admin API details) be submitted directly to support for investigation.
Status: Unresolved/ongoing. Key open questions: root cause, scope across API versions and admin UI, and whether a permanent fix or recommended mitigation exists.
Hi all,
The generic “Resulting order was not persisted” error message could be related to several issues.
If you have specific examples, or can share the steps of how you are able to replicate using the Admin APIs, please reach out directly to support.
Thanks