BUG #31629
Replies: 1 comment
-
I found some similar discussions regarding issues with report generation in Superset:
Common causes of failure when generating screenshots for dashboards in Superset include Selenium timeout errors. You can try increasing the timeout values in the # Increase screenshot timeouts
SCREENSHOT_LOCATE_WAIT = 100
SCREENSHOT_LOAD_WAIT = 600 Additionally, configuring the Chrome WebDriver with appropriate options can help prevent failures: # Configure Chrome WebDriver options
WEBDRIVER_OPTION_ARGS = [
"--force-device-scale-factor=2.0",
"--high-dpi-support=2.0",
"--headless",
"--disable-gpu",
"--disable-dev-shm-usage",
"--no-sandbox",
"--disable-setuid-sandbox",
"--disable-extensions",
]
WEBDRIVER_CONFIGURATION = {"service_log_path": "/dev/null"} These configurations help ensure that the WebDriver operates in a headless mode with sufficient resources and time to generate the screenshots successfully [4]. To continue talking to Dosu, mention @dosu. Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other |
Beta Was this translation helpful? Give feedback.
-
Environment: Docker Compose on AWS EC2
Issue: When scheduling a report in Superset:
Selecting the chart option successfully generates a report.
Selecting the dashboard option fails, and the report is not generated.
Error:
Report Schedule execution failed when generating a screenshot.
Notification sent with error.
Beta Was this translation helpful? Give feedback.
All reactions