adayush commented on issue #38216: URL: https://github.com/apache/superset/issues/38216#issuecomment-3958117060
For the checks 1, 2, 3 that you mentioned: If it was a config issue, I think all reports would have faced the same problem. But some reports are getting triggered fine while some are not getting triggered I'll give you examples: ### Report 1 1. Schedule is reflected in DB, timezone is correct 2. beat logs show report.schedule (i would see it even if there are no reports scheduled, this is my understanding) 3. At the time of schedule, celery logs show `Executing alert/report` and I get the report emailed ### Report 2 1. Schedule is reflected in DB, timezone is correct 2. beat logs show report.schedule (i would see it even if there are no reports scheduled, this is my understanding) 3. At the time of schedule, there are no celery logs -- 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]
