GitHub user dosubot[bot] added a comment to the discussion: Report Schedule is still working, refusing to re-compute.
<!-- Greeting --> Hi @bug-coder-007! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the superset team. <!-- Answer --> This error means Superset thinks the previous report run is still in progress ("working"), so it blocks new runs to avoid overlap. This usually happens if a previous report got stuck—often due to issues with Celery workers, browser/Chromedriver misconfiguration, or using SQLite as the metadata DB (which is not recommended for production) [[source](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/commands/report/execute.py)]. To resolve this: - Make sure your Celery workers are running and healthy, and that they can communicate with Redis and your metadata DB [[source](https://github.com/apache/superset/discussions/31647)]. - Double-check your Chrome/Chromedriver setup. The versions must match, and your `superset_config.py` should specify the correct path to Chromedriver in `WEBDRIVER_CONFIGURATION['service']['executable_path']` (not `WEBDRIVER_EXECUTABLE_PATH`, which is ignored) [[source](https://github.com/apache/superset/discussions/34053)]. - If you’re using SQLite for metadata, switch to PostgreSQL. SQLite can cause jobs to get stuck due to poor datetime handling [[source](https://github.com/apache/superset/issues/31625)]. - If a report is stuck, restarting the Celery worker(s) often clears the "working" state. In rare cases, you may need to manually update the report execution log in the database to reset the state. If you still don’t get emails, check for earlier errors in the logs—often a screenshot or browser config error is the root cause. Let me know if you need help with specific config examples or log analysis! <!-- 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/2108652e-76f7-4813-8129-4e13616b5776?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/2108652e-76f7-4813-8129-4e13616b5776?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/2108652e-76f7-4813-8129-4e13616b5776?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/2108652e-76f7-4813-8129-4e13616b5776?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/2108652e-76f7-4813-8129-4e13616b5776?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/2108652e-76f7-4813-8129-4e13616b5776?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/2108652e-76f7-4813-8129-4e13616b5776?feedback_type=other)</sup> [](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/34121) GitHub link: https://github.com/apache/superset/discussions/34121#discussioncomment-13720448 ---- 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]
