{"section":"known-issues","requestedLocale":"en","requestedSlug":"delay-to-register-cancelreason-in-the-order-json","locale":"en","slug":"delay-to-register-cancelreason-in-the-order-json","path":"docs/en/known-issues/Order Management/delay-to-register-cancelreason-in-the-order-json.md","branch":"main","content":"## Summary\n\n\nDue to the way the order update flow is executed from any status to canceled, it is possible that the Order system takes a while to register the CancelReason in the order json, causing a brief inconsistency scenario if the Json is consulted or used a few seconds after the cancel action;\n\nA practical example is the use of this field in the `vtexcommerce-order-cancelled` template, because as the save process may take a while it is possible that the email sending will not deliver this data to the end user because the email sending is asynchronous to the cancellation flow;\n\n\n##\n\n## Simulation\n\n\nnot possible to simulate it.\nBut it can be observed in the timeline of a canceled order, once that the `cancellationReason` property is used in the store template.\n\n\n##\n\n## Workaround\n\n\nIn case the failure impacts the get order process, we recommend that a new get be made;"}