SubscriptionErrorEmail not sending any email

[LucBanda]

Describe the bug

When user payment is failed, the webhook tries to send an email to the customer

This email is never sent
There is no error raising, the task in celery stays in "started" state
Celery logs shows that the task is ignored

Steps to reproduce

either setup a stripe test account and use a test card to simulate a subscription payment failure.
-> Subscription error email is not sent

OR

pnpm saas backend shell
python manage.py shell

from types import SimpleNamespace
customer=SimpleNamespace()
customer.subscriber = SimpleNamespace()
customer.subscriber.email = "test@email.com"
from apps.finances import notifications
notifications.SubscriptionErrorEmail(customer=customer).send()

System Info

fresh install of saas boilerplate
ubuntu 24.04.2

Logs

Click to expand!

celery_default-1  | [2025-06-21 07:34:34,945: INFO/MainProcess] Task common.emails.send_email[c4e8d92d-8793-443d-a7b8-0a401637f3fe] received
celery_default-1  | [2025-06-21 07:34:35,037: INFO/ForkPoolWorker-14] Task common.emails.send_email[c4e8d92d-8793-443d-a7b8-0a401637f3fe] ignored```
</details>

### Validations

- [x] Follow our [Code of Conduct](https://github.com/apptension/saas-boilerplate/blob/master/CODE_OF_CONDUCT.md).
- [x] Read the [Contributing Guidelines](https://github.com/apptension/saas-boilerplate/blob/master/CONTRIBUTING.md).
- [x] Read the [docs](https://docs.demo.saas.apptoku.com/).
- [x] Check that there isn't [already an issue](https://github.com/apptension/saas-boilerplate/issues) that reports the same bug to avoid creating a duplicate.
- [x] Check that this is a concrete bug. For Q&A open a [GitHub Discussion](https://github.com/apptension/saas-boilerplate/discussions) or join our [Discord Chat Server](https://discord.apptension.com).

[wang2-lat]

Worth checking if your Celery worker has the correct email backend configured in settings. Also verify SMTP credentials are accessible from the worker's environment - common gotcha is when Django shell has different env vars than the Celery process. You can test with celery -A config worker -l debug to see actual connection attempts.

[LucBanda]

The issue is identified and the fix is in PR

[wang2-lat]

Thanks for the quick turnaround! I'll keep an eye on the PR and test it once merged.