apache/superset · error · ReportScheduleCsvFailedError
Report Schedule execution failed when generating a csv.
Error message
Report Schedule execution failed when generating a csv.
What it means
Error "Report Schedule execution failed when generating a csv." thrown in apache/superset.
Source
Thrown at superset/commands/report/execute.py:1158
if self._report_schedule.type == ReportScheduleType.REPORT:
raise
raise ReportScheduleDataFrameTimeout() from ex
except ReportExecutionBudgetExceededError:
raise
except Exception as ex:
elapsed_seconds = (
datetime.now(timezone.utc).replace(tzinfo=None) - start_time
).total_seconds()
logger.error(
"DataFrame generation failed after %.2fs - execution_id: %s",
elapsed_seconds,
self._execution_id,
)
raise ReportScheduleDataFrameFailedError(
f"Failed generating dataframe {str(ex)}"
) from ex
if dataframe is None:
raise ReportScheduleCsvFailedError()
return dataframe
def _update_query_context(
self,
failed_error: type[CommandException] = ReportScheduleCsvFailedError,
) -> None:
"""
Update chart query context.
To load data from the endpoint the chart must have been saved
with its query context. For charts without saved query context we
get a screenshot to force the chart to produce and save the query
context. ``failed_error`` lets the caller surface a format-specific
failure (e.g. Excel vs CSV) when the screenshot fallback fails.
"""
try:
self._get_screenshots()
except (View on GitHub (pinned to f4587218dd)
Solutions
- Verify the chart query succeeds and the worker has write access to its temp storage; then retry the schedule.
When it happens
Trigger: CSV generation fails during report schedule execution.
Common situations: Report schedule execution aborted because CSV/dataframe generation failed upstream.
AI-assisted analysis of apache/superset@f4587218dd (2026-08-14).
Data as JSON: /api/errors/d253997bd8c0fd18.
Report an issue: GitHub.