-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Subscription processing failing repeatedly #13
Comments
Thanks for bringing this to my attention. I will look into this. In the mean time if you are able to provide steps in a sample store to reproduce this bug, it would help me identify the root cause. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Certain subscriptions are being processed repeatedly. It seems that the payment is failing (denied by the gateway), triggering the
FailureDispatcher#dispatch
method, which contains a call toorder.cancel!
I'm not sure why but some orders already appear to be cancelled before they get here, producing the following error:
This causes the job to fail and enter the retry queue, this cycle is repeated until the max failed attempts number is hit.
Maybe we can change
order.cancel!
toorder.cancel
to make it fail silently? I haven't identified why these orders are reaching the failure dispatcher with a canceled state.The text was updated successfully, but these errors were encountered: