venkatamandavilli-code commented on issue #39967: URL: https://github.com/apache/superset/issues/39967#issuecomment-4471313526
Thanks for reporting this issue and including the stack trace. The behavior seems related to datasource permission validation rather than the dataset itself actually being deleted. From the logs, it looks like Superset is failing during the datasource permission check (`check_datasource_perms`) and then returning the generic “dataset no longer exists” message afterward. In some cases, this can happen when the chart metadata, datasource ID, or security context becomes inconsistent after chart updates or datasource changes. It may help to verify: * whether the datasource ID referenced by the chart still matches the active dataset * whether role permissions were updated recently * whether cached chart metadata is referencing an older datasource state * whether the same issue occurs with admin-level access The `403` response during `explore_json` also suggests there may be a permission or security validation issue happening before the chart render completes. Thanks again for documenting the logs and reproduction steps clearly. -- 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]
