mahendra commented on issue #5294: Scheduled email reports for Slices / 
Dashboards
URL: 
https://github.com/apache/incubator-superset/pull/5294#issuecomment-413714805
 
 
   @mmuru I think I figured out your problems
   
   1) `Could not build url for endpoint u'Superset.dashboard'` - this is 
because in the schedule screen, you may not have configured a dashboard. Looks 
like the dashboard is set to `None`. Does your schedules dashboard have a 
`None` entry in it?
   
![image](https://user-images.githubusercontent.com/115988/44239676-5b4cc600-a16f-11e8-9a24-713691539fd6.png)
   
   I have pushed out a change to prevent this situation. Can you please 
change/update/edit and try again?
   
   2) If you are having issues with ChromeDriver, can you try defaulting to 
Firefox and try?
   
   3) I will take that as a feature request. Can you please create one on 
Github and assign it to me? I will work on it after this PR is merged (if it is 
merged :-) )
   
   4) The crontab UI is working as expected. Let me try to explain how this is 
supposed to work.
   * As per `CELERYBEAT_SCHEDULE`, every hour at the 1st minute, we fire off 
the `email_reports.schedule_hourly` task. This is meant to run _exactly once_ 
every hour.
   * `email_reports.schedule_hourly` goes through all the scheduled entries and 
figures out if any job needs to be executed in that particular hour.
   * If there are tasks that need running, `email_reports.schedule_hourly` will 
schedule them with celery (using the `eta` argument).
   
   I hope this clears up your questions.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to