dosubot[bot] commented on issue #33606: URL: https://github.com/apache/superset/issues/33606#issuecomment-2918862249
<!-- Answer --> The 404 error from your network request to `/api/v1/chart/27` indicates that Superset cannot find the chart or its required resources in production, even though it works locally. Based on the Superset code and recent updates, this can happen if: - The chart with ID 27 does not exist in the production database, or its datasource is missing or misconfigured. The endpoint will return a 404 if either the chart or its datasource cannot be found or loaded [[source]](https://github.com/apache/superset/blob/master/superset/charts/data/api.py). - There are permission issues or missing roles after recent API changes. Superset migrated from `/superset/slice_json/<id>` to `/api/v1/chart/<id>/data/`, and permissions must be updated accordingly. Ensure your production roles have `can read on Chart` [[source]](https://github.com/apache/superset/blob/master/UPDATING.md). - The query context for the chart is missing or corrupted in production. If the chart’s saved query context cannot be loaded, the API will not return data [[source]](https://github.com/apache/superset/blob/master/superset/charts/data/api.py). - The frontend and backend versions are mismatched, or migrations are incomplete, which can cause endpoints to fail. Since you confirmed the chart exists in the database, double-check that its datasource (table or dataset) also exists and is accessible in production. Try opening the chart directly in the Superset UI in production—if it fails there, the issue is with the chart or datasource, not embedding. If you recently upgraded or changed your Superset deployment, ensure all database migrations have run and that your roles/permissions are up to date. If you have custom roles, verify that they include the new permissions for chart access. If you can, inspect the Superset server logs right after the 404 occurs for any traceback or error message related to chart or datasource lookup. This can help pinpoint if it’s a missing chart, missing datasource, or a permissions/configuration issue. Let me know if you find any error messages in the logs or if the chart fails to load in the Superset UI itself. That will help narrow down the root cause. <!-- Dosu Comment Footer --> *To reply, just mention my name [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/eabcf124-dd44-4d0e-b2a4-dedd2759f20b?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/eabcf124-dd44-4d0e-b2a4-dedd2759f20b?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/eabcf124-dd44-4d0e-b2a4-dedd2759f20b?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/eabcf124-dd44-4d0e-b2a4-dedd2759f20b?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/eabcf124-dd44-4d0e-b2a4-dedd2759f20b?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/eabcf124-dd44-4d0e-b2a4-dedd2759f20b?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/eabcf124-dd44-4d0e-b2a4-dedd2759f20b?feedback_type=other)</sup> [](https://go.dosu.dev/discord-bot) [! [Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/issues/33606) -- 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]
