GitHub user dosubot[bot] added a comment to the discussion: Weird behavior and errors in Alert&Reports with playwright.
<!-- Greeting --> Hi @fractalthoughts312! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the superset team. <!-- Answer --> The SoftTimeLimitExceeded errors you’re seeing are Celery’s way of killing tasks that run too long—usually because Playwright is waiting for the page or chart to finish loading. This can happen if the browser is slow to start, the dashboard is heavy, or there are resource constraints in Docker. After a failure, Superset’s retry/error cache TTL logic will eventually trigger a retry, which is why you get the report later without any config changes. A few things to check and try: - Recent Docker images do **not** include Chromium by default. If you’re using Playwright for screenshots, make sure your Docker build sets `INCLUDE_CHROMIUM=true` or that Chromium is present in your image, or Playwright tasks will silently fail or hang [source](https://github.com/apache/superset/pull/34258). - Change `SCREENSHOT_PLAYWRIGHT_WAIT_EVENT` from `"load"` to `"domcontentloaded"`. This is now the recommended default and has resolved similar Playwright timeout issues for others [source](https://github.com/apache/superset/issues/34076) [source](https://github.com/apache/superset/pull/34114). - Monitor your Docker container’s CPU and memory usage. Playwright/browser tasks are resource-intensive and can easily hit limits in constrained environments, causing timeouts [source](https://github.com/apache/superset/issues/33602). - Review your Celery worker concurrency and timeouts. If you have a lot of reports or heavy dashboards, you may need to increase resources or adjust Celery’s soft/hard timeouts. The default soft time limit for thumbnail/report tasks is 300s, but this can be customized in your Celery config [source](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/config.py). - The retry/delay you observe is due to Superset’s screenshot cache logic: after a failure, it waits for the error cache TTL to expire before retrying the task [source](https://github.com/apache/superset/utils/screenshots.py). If you still see intermittent failures, check logs for resource exhaustion, Playwright/Chromium errors, or network issues between your worker and the Superset web UI. Also, ensure your WebDriver args include recommended flags like `--headless`, `--no-sandbox`, and `--disable-gpu` for stability in Docker [source](https://github.com/apache/superset/issues/33602). <!-- 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/6e0e7541-ae54-4c11-9fa3-ab8ffc1e7ae6?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/6e0e7541-ae54-4c11-9fa3-ab8ffc1e7ae6?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/6e0e7541-ae54-4c11-9fa3-ab8ffc1e7ae6?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/6e0e7541-ae54-4c11-9fa3-ab8ffc1e7ae6?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/6e0e7541-ae54-4c11-9fa3-ab8ffc1e7ae6?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/6e0e7541-ae54-4c11-9fa3-ab8ffc1e7ae6?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/6e0e7541-ae54-4c11-9fa3-ab8ffc1e7ae6?feedback_type=other)</sup> [](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=github)& nbsp;[](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/discussions/34297) GitHub link: https://github.com/apache/superset/discussions/34297#discussioncomment-13873425 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
