Hariprasath-0018 commented on issue #37357: URL: https://github.com/apache/superset/issues/37357#issuecomment-3783670095
Hi @dosu Thanks for the detailed checklist! I went through each point and here’s the status of my Superset setup: 1. Config file placement: I don’t have a superset_config_docker.py in my directory. The files I have are: superset_config.py superset_config_docker_light.py superset_config_local.example superset_test_config_light.py 2. Feature flags: ✅ Already done. 3. Celery beat schedule: ✅ Already done. 4. Playwright/Chromium: Installed manually, but had to change .env to: ENABLE_PLAYWRIGHT=true INCLUDE_CHROMIUM=true before it would recognize Playwright. 5. SMTP config: ✅ Already done. 6. Database migrations: ✅ Tables migrated successfully. 7. Active schedules: ✅ Schedules are active. 8. Logs: Worker starts fine (celery@... ready) and connects to Redis. Scheduler logs show startup, but there’s no evidence of tasks being sent. 9. Execution logs: ReportExecutionLog table is empty. Despite everything above being configured, emails are still not being sent. -- 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]
