...
| Frequency | Format for Start and End | Explanation | Example |
|---|---|---|---|
| daily | HH:MM:SS HH:MM | 24:00 means the end of the day, and makes sense only as period end. 00:00 means the beginning of the day. Leading zeros can be omitted. | 14:15 23:45 |
| weekly | Wday HH:MM:SS Wday HH:MM | Wday is one of "Mon", "Tue" ... "Sun" (Case-insensitive). Monday is considered first, Sunday last. Start: Sun 14:00, End Wed 17:00 will cover sun, mon, tue, wed; Start: Fri 17:00, End Mon 09:00 will cover fri, sat, sun, mon. | Fri 14:45 |
| monthly | D HH:MM:SS | D is the day of the month, 1..31. -D counts from the end of the month; -1 is the last day of the month, -2 the second to last etc. | 4 17:00 -1 00:00 |
| yearly | M D HH:MM:SS | M is the month number, 1..12. D is the day number, 1..31. | 12 24 19:00 13 31 24:00 |
One-off
...
/non-recurring scheduled and on-demand Reports
For scheduled non-recurring reports, the start and end properties must fully describe a date and time for the reporting period.
All the formats described in on the Supported Time Formats page are supported here, but relative formats including the relative formats like "midnight - 14 days".
Relative formats work fine for generating reports on-demand from the GUI (e.g. a report starting "yesterday" and ending "now" will cover precisely the last 24 hours).
However, using relative formats with scheduled one-off reports will likely now - 20 minutes") may lead to unexpected behaviour and should thus be avoided.
We Overall we recommend that you stick to one of the unambiguous absolute formats like "30-mar-2014 16:31:53" or the ISO8601-style "2015-03-30T16:31:53" for clarity, and only use relative formats for on-demand reports.
Business hours reporting works as described above.