dosubot[bot] commented on issue #36439: URL: https://github.com/apache/superset/issues/36439#issuecomment-3616589834
<!-- Answer --> Thanks for confirming the changes and that manual CSV downloads work. Given your steps and Superset 6.0.0rc3, here are the most likely causes and next checks: - Scheduled CSV reports use the chart’s saved query context, not the live one from the browser. If the query context references columns that no longer exist in the dataset (for example, after schema changes or column removal), the scheduled report will return only headers with no data—even if the columns look correct in the UI. Manual downloads use the current context, so they work as expected [cite](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/commands/report/execute.py#L380-L901) [cite](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/charts/data/api.py#L64-L465). - Recent changes to CSV export (like streaming for large datasets) could introduce regressions, but these mostly affect performance and chunking, not empty data for small exports [cite](https://github.com/apache/superset/pull/35478). - Scheduled reports strictly enforce row limits and filters set in the chart configuration. If a filter or limit causes the query to return zero rows, you’ll get only headers in the CSV—even if manual export ignores these limits [cite](https://github.com/apache/superset/discussions/32747). - If you deploy Superset under a subpath (using SUPERSET_APP_ROOT), there’s a known bug in 6.0.0rc2/rc3 where CSV export URLs may be broken, causing empty CSVs. This only applies if you use a subpath [cite](https://github.com/apache/superset/issues/35027). **What to try next:** - Double-check that all columns referenced in the chart’s query context exist in the dataset. Try re-saving the chart after making column changes, then re-run the report. - Review chart-level filters and row limits—scheduled reports enforce these strictly. - If you use a subpath, test CSV export with SUPERSET_APP_ROOT unset to rule out URL issues. - If possible, enable debug logging for the report worker to catch silent errors or query results. If none of these resolve it, try creating a minimal chart and dataset (not from SQL Lab) and see if the issue persists. This can help isolate whether the problem is dataset-specific or a broader regression. <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/5f7b1ec0-49d9-4f3e-9534-bdd76a8857b3?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/5f7b1ec0-49d9-4f3e-9534-bdd76a8857b3?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/5f7b1ec0-49d9-4f3e-9534-bdd76a8857b3?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/5f7b1ec0-49d9-4f3e-9534-bdd76a8857b3?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/5f7b1ec0-49d9-4f3e-9534-bdd76a8857b3?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/5f7b1ec0-49d9-4f3e-9534-bdd76a8857b3?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/5f7b1ec0-49d9-4f3e-9534-bdd76a8857b3?feedback_type=other)</sup> [](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=github) [](https://cursor.com/link/prompt?text=Thanks%20for%20confirming%20the%20changes%20and%20that%20manual%20CSV%20downloads%20work.%20Given%20your%20steps%20and%20Superset%206.0.0rc3%2C%20here%20are%20the%20most%20likely%20causes%20and%20next%20checks%3A%0A%0A-%20Scheduled%20CSV%20reports%20use%20the%20chart%E2%80%99s%20saved%20query%20context%2C%20not%20the%20live%20one%20from%20the%20browser.%20If%20the%20query%20context%20references%20columns%20that%20no%20longer%20exist%20in%20the%20dataset%20%28for%20example%2C%20after%20schema%20changes%20or%20column%20removal%29%2C%20the%20scheduled%20report%20will%20return%20only%20headers%20with%20no%20data%E2%80%94even%20if%20the%20columns%20look%20correct%20in%20the%20UI.%20Manual%20downloads%20use%20the%20current%20context%2C%20so%20they%20work %20as%20expected%C2%A0%5Bcite%5D%28https%3A//github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/commands/report/execute.py%23L380-L901%29%C2%A0%5Bcite%5D%28https%3A//github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/charts/data/api.py%23L64-L465%29.%0A%0A-%20Recent%20changes%20to%20CSV%20export%20%28like%20streaming%20for%20large%20datasets%29%20could%20introduce%20regressions%2C%20but%20these%20mostly%20affect%20performance%20and%20chunking%2C%20not%20empty%20data%20for%20small%20exports%C2%A0%5Bcite%5D%28https%3A//github.com/apache/superset/pull/35478%29.%0A%0A-%20Scheduled%20reports%20strictly%20enforce%20row%20limits%20and%20filters%20set%20in%20the%20chart%20configuration.%20If%20a%20filter%20or%20limit%20causes%20the%20query%20to%20return%20zero%20rows%2C%20you%E2%80%99ll%20get%20only%20headers%20in%20the%20CSV%E2%80%94even%20if%20manual%20export%20ignores%20these%20limits%C2%A0%5Bcite%5D%28https%3A//github.com/apa che/superset/discussions/32747%29.%0A%0A-%20If%20you%20deploy%20Superset%20under%20a%20subpath%20%28using%20SUPERSET_APP_ROOT%29%2C%20there%E2%80%99s%20a%20known%20bug%20in%206.0.0rc2/rc3%20where%20CSV%20export%20URLs%20may%20be%20broken%2C%20causing%20empty%20CSVs.%20This%20only%20applies%20if%20you%20use%20a%20subpath%C2%A0%5Bcite%5D%28https%3A//github.com/apache/superset/issues/35027%29.%0A%0A%2A%2AWhat%20to%20try%20next%3A%2A%2A%20%20%0A-%20Double-check%20that%20all%20columns%20referenced%20in%20the%20chart%E2%80%99s%20query%20context%20exist%20in%20the%20dataset.%20Try%20re-saving%20the%20chart%20after%20making%20column%20changes%2C%20then%20re-run%20the%20report.%0A-%20Review%20chart-level%20filters%20and%20row%20limits%E2%80%94scheduled%20reports%20enforce%20these%20strictly.%0A-%20If%20you%20use%20a%20subpath%2C%20test%20CSV%20export%20with%20SUPERSET_APP_ROOT%20unset%20to%20rule%20out%20URL%20issues.%0A-%20If%20possible%2C%20enable%20debug%20logging%20for%20the%20report%20w orker%20to%20catch%20silent%20errors%20or%20query%20results.%0A%0AIf%20none%20of%20these%20resolve%20it%2C%20try%20creating%20a%20minimal%20chart%20and%20dataset%20%28not%20from%20SQL%20Lab%29%20and%20see%20if%20the%20issue%20persists.%20This%20can%20help%20isolate%20whether%20the%20problem%20is%20dataset-specific%20or%20a%20broader%20regression.) [](https://go.dosu.dev/discord-bot) [](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/issues/36439) -- 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]
