Scheduled Reports don't work

I am trying to configure scheduled reports without luck so far. I don't get any errors in the log file, still no report is being sent.

These are my scheduled report settings

This is how I schedule the report here

Is there anything else that I need to do?

It doesn't look correct. Your daily report is for more than 24 hours period.

So it should be like this?

1. So daily reports should be no longer than 23:59 hours?
2. Weekly reports should be no longer than 6 days and 23:59 hours?
3. How about monthly reports? Various months have various length - 28,29,30,31 days. How can we schedule those?

Thanks!

Monthly reports shouldn't be longer than a month. I'm assuming calendar will handle it correctly.

Interesting, this is something that should be tested, I see two scenarios:

1. We use a month with 30 days and we set the report from 1st 00:00 until 30th 23:59. Will we get a report for 31 days for the next month that has 31 days?
2. We use a month with 31 days and we set the report from 1st 00:00 until 31th 23:59. Will we get a report for the months with 30 days or less? (this seems to fall into the initial problem that I ran into).

Which of the two would you recommend?

Either one should work, I believe.

So, after 24 hours and a few more scheduled reports, I still don't get anything.

Here are two example Calendars:

Calendar1
Calendar2

I have also linked them to the Trips report as explained on other threads.

Couple of questions which will help me troubleshoot:

1. If I have a daily report scheduled from 9:30 to 10:00, when will the report run? Everyday at 10:00?
2. How can I decode the calendar data parameter?

1. Yes.
2. It should be base64.

Thanks, the data parameter and time timestamps look correct.

Can there be any other reason why the scheduled reports are failing?

There's a known issue, but I don't think it affects daily reports. You also mentioned no warnings in the log.

Is this the issue you are referring to: https://github.com/traccar/traccar/issues/5496

Yes.

Definitely not that one - no such warnings in the logs. I will try to set some additional logging, hopefully I will catch the error.