[Question] Email notifications and webhook notifications not working

[edd080]

Pre-work

• I have read the docs.
• I have searched open and closed issues.
• I agree to follow this project's Code of Conduct.

Description

After updating I noticed that after every Speedtest the notification email is not received, however when sending a test email this is received as expected.
I also noticed that ntfy will be deprecated so I have enabled the general Webhook notification, which again receives the test webhook successfully but I do not receive any notification after an actual Speedtest.
The actual ntfy setting is working as expected so no issues there.

Expected Behavior

To receive an email and webhook notification to my email and ntfy setup.

Steps to Reproduce

Test both email and webhook settings to make sure the test is received and perform a speedtest run, where the notifications are not received.

Deployment Environment

Docker Compose

Application Information

{"environment":{"application_name":"Speedtest-Tracker","laravel_version":"12.40.2","php_version":"8.4.14","composer_version":"2.9.2","environment":"production","debug_mode":false,"url":"   ","maintenance_mode":false,"timezone":"UTC","locale":"en"},"cache":{"config":true,"events":true,"routes":true,"views":true},"drivers":{"broadcasting":"null","cache":"database","database":"sqlite","logs":"stderr","mail":"smtp","queue":"database","session":"database"},"storage":{"\/app\/www\/public\/storage":false},"filament":{"version":"v4.1.0","packages":"filament, forms, notifications, support, tables, actions, infolists, schemas, widgets","views":"NOT PUBLISHED","blade_icons":"CACHED","panel_components":"CACHED"},"livewire":{"livewire":"v3.7.0"},"speedtest_tracker":{"version":"v1.10.1"}}

What browser(s) are you seeing the problem on?

Chrome, Firefox

Logs

[JPCompany544]

Looks like the test notifications work because they bypass the event pipeline, but the actual Speedtest run isn’t firing the notification job after the update.

This usually comes from one of three spots:

1. The Speedtest job isn’t dispatching the notification event

In 1.10.x there were changes around notification triggers.
If the SpeedtestResult event isn’t firing, neither mail nor webhook will run — but test notifications will still work.

2. Queue worker isn’t processing queued notifications

Your app is using the database queue driver.
If the queue isn't running inside your Docker environment, queued mails/webhooks will just sit in the jobs table.

You can confirm by checking:

php artisan queue:work

or the jobs + failed_jobs tables.

3. Cached config after upgrade

Because config/routes/events are cached in your env:

"cache":{"config":true,"events":true,"routes":true}

If the notification bindings changed but the cache wasn’t cleared, only test sends will work.

Try inside the container:

php artisan optimize:clear

If you want, I can walk you through confirming which of the three is actually breaking the notification chain.

[edd080]

Hello I have run the php optimizer command and did another Speedtest run I receive the ntfy notification but still no email or webhook notification.

[edd080]

Forgot to mention this is usually not the first time that after updating, the email notifications do not work, @alexjustesen then issues a fix for this and it gets resolved , so not sure if there is something different this time.
Thank you for your help.

[JPCompany544]

Hi @edd080,

Thanks for the details. From what you’re describing, it looks like the Speedtest job is firing for ntfy, but email and webhook notifications aren’t making it through the pipeline. This usually comes down to one of three things:

Queue worker not processing jobs – since you’re using the database queue driver, queued mails/webhooks will sit idle if no worker is running.

Notification pipeline changes in v1.10.x – test notifications bypass the full pipeline, so they can succeed while real events fail.

Cached config/routes/events – if event bindings changed but caches weren’t cleared, only test sends will work.

You already ran php artisan optimize:clear, which fixes the cache part and allows ntfy notifications, but the email/webhook issue points to either a queue or pipeline problem.

I can walk you through confirming exactly where the break is and get all notifications working reliably. I usually handle this as a short consulting setup (~30–45 min), with a step-by-step resolution that fixes it every time.

If you want, I can prepare that guide for your environment.

—JPCompany544

[edd080]

The ntfy notifications where always working before and after the update, the issue is with the email notifications and with the webhooks (since ntfy will be deprecated). Not sure what else to do at this point, your guidance is appreciated.
Thanks.

[svenvg93]

Just to confirm: Is this behavior occurring after a scheduled test, or when manually triggering a test in the UI? We no longer send notifications (Mail, Webhook, or Database) for manually triggered tests.”

[edd080]

Just to confirm: Is this behavior occurring after a scheduled test, or when manually triggering a test in the UI? We no longer send notifications (Mail, Webhook, or Database) for manually triggered tests.”

Had a scheduled test occuring this morning, I received the ntfy notification (the one that will be deprecated) but received no email or webhook notification.
A manual speedtest sends a notification to ntfy just fine, may I ask why the notifications for manual runs has been stopped for mail and webhook?

[svenvg93]

Had a scheduled test occuring this morning, I received the ntfy notification (the one that will be deprecated) but received no email or webhook notification

Thanks for confirming, I will look into it.

A manual speedtest sends a notification to ntfy just fine, may I ask why the notifications for manual runs has been stopped for mail and webhook?

We’re currently refactoring the notification logic to simplify it. Custom channels like ntfy will be deprecated and replaced with Apprise. We also didn’t see a clear benefit in sending a notification when someone is already logged in to run the test.

Additionally, the general webhook does not work reliably with ntfy, as ntfy expects a specific payload format. While the test notification matches this format, the other notifications do not. For now you can still use the dedicated channel, when Apprise is released you can switch that Apprise.

[edd080]

Thanks for your reply and checking on this; so when Apprise is released I can then set it up to send notifications to ntfy?

[svenvg93]

Thanks for your reply and checking on this; so when Apprise is released I can then set it up to send notifications to ntfy?

Yess but you will need an Apprise Sidecar container for it. We will update the docs before the release 😄