flagsmith
flagsmith copied to clipboard
When a user is issued a refund in Chargebee the subscription does not fire a cancel webhook
Describe the bug
When a user is issued a full refund, the subscription webhook does not fire, so subsequent cancelation of the user failed. This is atypical behaviour, and so far only a single internal Flagsmith staff had the issue raised when he was testing the workflow.
To Reproduce
Steps to reproduce the behavior:
- Create an account and pay for it with a credit card.
- Get a Flagsmith Chargebee staff user to issue you a full refund.
- Delete your user account and watch the 500 error through the Chargebee failure, since the Subscription is no longer cancelable as it has been issued a full refund.
Expected behavior
Either capture a full refund webhook, which should be possible, or add a get request to a subscription after failure to check if the cancelation had already proceeded in which case there should be no reason to fail the cancelation step.
Sentry
How are you running Flagsmith?
- [ ] Self Hosted with Docker
- [ ] Self Hosted with Kubernetes
- [x] SaaS at flagsmith.com
- [ ] Some other way
@matthewelwell and I talked about this as a low priority bugfix, since we shouldn't see it with regular users.