eohulse opened a new issue #13392: URL: https://github.com/apache/superset/issues/13392
Some CRON schedules when saved in the database cannot be read back. For example, when scheduling a report to be sent every day at 20:00, 20:05, and 20:10 (CRON 0-10/5 20 * * *), one can save this to the database. However when the Alerts & reports page is reloaded the page does not load any report, and an error appear in the log indicating 10/5 cannot be handled. ### Expected results Since I generated the CRON using the UI, superset should be able to read them back from the database. ### Actual results No reports can be loaded or created anymore. The whole alert/reporting functionality seemed to be broken because o f the error. #### Screenshots  #### How to reproduce the bug 0. Set up a docker enabling reports/alerts using postgres. (Followed this [template](https://github.com/apache/superset/blob/6b565707f03a0c592a85deb112c1d1d67903fc96/docs/src/pages/docs/installation/email_reports.mdx) 1. Go to Settings > Alerts & reports > Reports 2. Click on '+ REPORT' 3. Set up a report to be sent, but use the following CRON: 0-10/5 20 * * * 4. Save the report 5. Go to the superset home page 6. Go back to the Alerts & reports page, the new report that was recently created is not listed (empty list) ### Environment (please complete the following information): - superset version: `1.01` - python version: `3.7.9` ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
