udayv2000 opened a new issue, #36602: URL: https://github.com/apache/superset/issues/36602
### Bug description After upgrading Apache Superset to **6.0.0rc4**, we started observing intermittent routing errors during normal application usage. The upgrade triggered the standard metadata database migration successfully. However, while using the Superset UI (navigating dashboards, charts, etc.), the application intermittently logs 404 NotFound and 405 MethodNotAllowed exceptions originating from Flask/Werkzeug routing. These errors did not occur prior to upgrading to the 6.0.0 RC build. ### Screenshots/recordings **Application logs show intermittent routing exceptions:** werkzeug.exceptions.NotFound: 404 Not Found werkzeug.exceptions.MethodNotAllowed: 405 Method Not Allowed **Exceptions originate from Flask request routing:** werkzeug/routing/map.py: match() flask/ctx.py: match_request() flask/app.py: raise_routing_exception() **Steps to Reproduce** Upgrade an existing Superset deployment to 6.0.0rc4 Allow metadata database migration to complete Use the Superset UI (dashboards, charts, navigation) Observe intermittent 404/405 routing exceptions in the application logs ### Superset version master / latest-dev ### Python version 3.9 ### Node version 16 ### Browser Chrome ### Additional context This behavior was not observed on earlier Superset versions. Since the database schema has been migrated, downgrading is not straightforward. Seeking guidance on whether this is a known issue in the 6.0 RC builds. ### Checklist - [x] I have searched Superset docs and Slack and didn't find a solution to my problem. - [x] 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. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
