Introduce more verbose logging for each step in the checkout process. This will help pinpoint exactly where a failure occurs—whether it’s during a hook, before/after order creation, or during payment processing. By logging each step, developers and support teams can quickly identify problematic areas without extensive debugging.
Describe alternatives you've considered
We considered handling all checkout steps in one atomic process, but this could lead to stability issues when a failure occurs. An alternative is to break the process down into smaller, idempotent steps, managed by a state machine. However, this is more complex and would require a broader refactor. Step-by-step logging offers a straightforward and less invasive solution.
Describe the solution you'd like
Introduce more verbose logging for each step in the checkout process. This will help pinpoint exactly where a failure occurs—whether it’s during a hook, before/after order creation, or during payment processing. By logging each step, developers and support teams can quickly identify problematic areas without extensive debugging.
Describe alternatives you've considered
We considered handling all checkout steps in one atomic process, but this could lead to stability issues when a failure occurs. An alternative is to break the process down into smaller, idempotent steps, managed by a state machine. However, this is more complex and would require a broader refactor. Step-by-step logging offers a straightforward and less invasive solution.
Additional context
pca54o-8fk-p2