Alerts and reports feature not working. URL not found

[Dens1002]

Bug description

Hey y'all, I've been trying to implement the alerts and reports feature but I've been getting the following error message: The requested URL was not found on the server. If you entered the URL manually please check your spelling and try again. I've defined the cookie domain parameter in the superset_confing.py file and I've checked that it matches superset's address. Other that that I haven't found any likely reasons for this error upon googling it. Any help is appreciated, thanks in advance!

Screenshots/recordings

No response

Superset version

4.1.3

Python version

3.9

Node version

16

Browser

Chrome

Additional context

No response

Checklist

• I have searched Superset docs and Slack and didn't find a solution to my problem.
• I have searched the GitHub issue tracker and didn't find a similar bug report.
• I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.

[dosubot[bot]]

The "URL not found" error for alerts and reports in Superset 4.1.3 is most often caused by the required feature flags not being enabled. Make sure you have "ALERT_REPORTS": True set in your FEATURE_FLAGS in superset_config.py. Depending on your use case, you may also need to enable related flags like ALERT_REPORT_TABS and ALERT_REPORTS_FILTER for dashboard tab and filter support source, source.

If the feature flag is disabled, Superset will return a 404 for all alerts and reports endpoints, which matches the error you're seeing source.

Also, for Superset 4.1.x and above, you need to have a headless browser (Playwright with Chrome is recommended) installed in your worker container, and the relevant feature flag set source.

Double-check your config for these flags and browser setup. If you still see the error after enabling the flags, please share the specific URL that fails and any relevant logs for deeper troubleshooting.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}    

[sfirke]

I have Alerts & Reports working great on 4.1.3 so I expect this is a matter of configuring your deployment. I'm going to convert this to a discussion, not a bug report, given that - but if we turn up something that needs fixing we can revisit that.

Can you share more about how you have Superset deployed? And try the steps here: https://superset.apache.org/docs/configuration/alerts-reports/#troubleshooting

[dosubot[bot]]

The "URL not found" error for alerts and reports in Superset is almost always caused by the ALERT_REPORTS feature flag not being enabled. This flag must be set to True in your superset_config.py under FEATURE_FLAGS for the endpoints and UI to be available. Without it, Superset will return a 404 for all alerts and reports routes, regardless of other configuration settings.

Make sure your superset_config.py includes:

FEATURE_FLAGS = {
    "ALERT_REPORTS": True,
    # ...other flags
}

You also need to have Celery (and a suitable broker like Redis or RabbitMQ) running, as alerts and reports depend on background tasks for scheduling and execution. If Celery isn't running, the UI may appear but reports won't actually process or send.

If you enable the flag and still see 404s, double-check that your Superset instance is loading the correct config file and that you don't have a typo in the flag name or config structure.

References:

• superset/config.py - ALERT_REPORTS flag and Celery requirements
• superset/views/alerts.py - Endpoint gating by feature flag
• superset/initialization/init.py - Menu registration and feature flag check

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}    

[sfirke]

@dosu this seems unlikely - if the user hadn't enabled the feature flag for Alerts & Reports, how would they have gotten to the point where it would say URL not found?

[dosubot[bot]]

You're right—under normal circumstances, if the ALERT_REPORTS feature flag is disabled, both the backend endpoints and the UI menu for Alerts & Reports are hidden, so users shouldn't be able to access those routes at all. However, there are rare cases where a user might see the UI but still get a 404 from the backend: for example, if the frontend is cached or out of sync after a config change, or in a multi-node deployment with inconsistent configs. But in a typical, single-node, freshly restarted deployment, the UI and endpoints are gated together by the flag, and a "URL not found" error would only occur if the flag is disabled or if there's a deployment/config drift issue. The backend checks the flag and returns a 404 if it's off, regardless of what the frontend shows (source).

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}