Schedules

Schedules enable automatic, time-based execution of reports. The generated PDFs can be sent via email, posted to a webhook, or stored on the file system.

Creating a Schedule

Navigate to Schedules in the sidebar
Click New Schedule
Fill in the fields:

Field	Description
Name	Schedule name
Report	Which report to execute
Environment	Which environment to run against (optional)
Cron Expression	Schedule timing (6-part, see below)
Timezone	Timezone for execution (default: Europe/Berlin)
Delivery Type	How to deliver the result
Parameters	Report parameters for execution

Cron Expressions

Schedules use 6-part cron expressions:

Second Minute Hour Day Month Weekday

Examples:

Expression	Meaning
`0 0 8 * * MON-FRI`	Weekdays at 8:00 AM
`0 0 6 1 * *`	1st of every month at 6:00 AM
`0 30 17 * * FRI`	Every Friday at 5:30 PM
`0 0 0 * * *`	Daily at midnight

Delivery Types

Email

The PDF is sent as an email attachment.

Field	Description
Recipients	List of email addresses (at least one required)
CC / BCC	Optional copy recipients
Subject	Email subject line
Body Template	Optional email body text

Webhook

The PDF is sent via HTTP request to a URL.

Field	Description
URL	Target URL
Method	POST or PUT (default: POST)
Headers	Optional HTTP headers

Folder (File System)

The PDF is stored on the file system.

Field	Description
Path	Target directory
Naming Pattern	Optional naming pattern for the file

Controls

Pause / Resume — Schedules can be paused and resumed at any time without deleting them
Execute Now — Manual trigger independent of the cron schedule
Test Mail — Send a test email to verify the SMTP configuration (email delivery only)

Execution History

Every execution is logged:

Field	Description
Status	RUNNING, SUCCESS, or FAILED
Start Time	When the execution started
End Time	When the execution finished
File Size	Size of the generated PDF
Error	Error message if FAILED
Recipients Notified	Number of notified recipients (for email)

The history is accessible in the schedule detail view.

Important

Schedules always render the deployed version of the report for the configured environment (snapshot), not the current editor state. If no deployment exists, the working copy with base config is used.