venkatamandavilli-code commented on issue #40047: URL: https://github.com/apache/superset/issues/40047#issuecomment-4471308076
Thanks for reporting this issue and sharing the logs in detail. The behavior seems consistent with the report execution state not being cleared correctly after an earlier task attempt. Based on the stack trace, it looks like Superset still considers the report execution as active (`Report Schedule is still working`) even after the worker process completes. In some cases, this can happen if the task state, Celery metadata, or report execution status becomes out of sync after a failed or interrupted run. It may help to verify: * whether stale task entries still exist in the Celery backend or metadata database * whether multiple scheduler/worker instances are picking up the same report simultaneously * whether report execution cleanup is completing correctly after exceptions * whether there were any environment or dependency updates during the last 10 days, even without container rebuilds The issue also feels somewhat similar to earlier report execution/state synchronization problems seen around Superset v5 alert/report workflows. Thanks again for documenting the logs and troubleshooting steps clearly. -- 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]
