6.9.10. Scheduling reports
Enterprise / Reports / Scheduled Reports / 2. How to schedule a report
Since version v1.0.3.83
1) Create a view first
Scheduled reports are always based on a saved view. If the view is not saved, it cannot be scheduled.
Steps:
1. Open Reports → Reports 1 – Activity
2. Set filters (period, users, jobs, activities, etc.)
3. Click Save changes in the view or Save as new view
2) Open the scheduling dialog
Once the view is saved, click Schedule report.
-
If the view is not saved you will get a warning.
-
If already scheduled, the dialog will open in edit mode.
Task editor window (Schedule report)
This dialog allows you to create or update a scheduled task for the current view.
Form settings explanation
|
Setting
|
Description
|
|
Starting date
|
Date when the task can start (yyyy/mm/dd).
|
|
Time
|
Time of day the task should run (hh:mm).
|
|
Repeat task
|
If enabled → task is Recurring. If disabled → task is Scheduled once.
|
|
Repeat every
|
Recurrence interval: Month / Week / Day / Hour
|
|
Destination directory
|
Folder where files are created (local only). Default: %program_data%\\TempReports\\Scheduled
|
|
Destination
|
Local / Azure Blob Storage / Azure File Storage
|
|
Azure profile
|
Required if destination is Azure. Select a profile created in Azure Profiles dialog.
|
|
File name
|
Base file name for report output.
|
|
Output formats
|
Multiple formats can be selected: XLS / CSV / JSON / XML
|
|
Send via email
|
Sends the report to recipients after generation (SMTP must be configured).
|
|
Recipients
|
List of ChronoScan users. Multiple emails separated by ;.
|
|
Force start from last generated report
|
If checked, next execution starts from the last execution period_to to avoid gaps.
|
|
Include activity description
|
Adds a new column with translated activity description.
|
|
Append timestamp to file name
|
If checked, filenames include _YYYYMMDDhhmmss.
|
|
Active
|
Enables or disables the scheduled task.
|
Info: When Starting date, Time, Repeat task or Repeat every changes, the Next execution panel is recalculated.
Next execution panel
Shows when the task will run next. Remember to click Save after making changes.
Output file naming
If Append timestamp is enabled, filenames will include:
|
<filename>_YYYYMMDDhhmmss-<execution_type>
|
Where:
-
execution_type = auto (automatic execution)
-
execution_type = manual (manual trigger)
-
If disabled → no timestamp suffix.
Azure destinations and profiles
If you choose Azure Blob Storage or Azure File Storage, you must create/select a profile.
How to create an Azure profile
1. Click Select profile → Manage profiles
2. Click Add
3. Choose Type:
How to get Azure URL and SAS Token (Azure Storage Explorer)
You can obtain the URL and SAS token directly from Azure Storage Explorer.
Steps
1. Open Azure Storage Explorer and connect to your Azure account.
2. Navigate to the storage account and choose:
* Example:
|
URL:
https://mystorageaccount.blob.core.windows.net/reports
SAS token:
?sv=2022-11-02&ss=bfqt&srt=sco&sp=rwdlacup&se=2026-05-01T00:00:00Z&st=2024-05-01T00:00:00Z&spr=https&sig=XXXXXXXX
|
* Use the URL and SAS token when creating the Azure profile in ChronoScan
Enterprise / Reports / Scheduled Reports / 3. Managing and monitoring scheduled report tasks
Under Reports → Scheduled reports you can manage and monitor all tasks.
Information columns
-
-
-
-
Task type (Scheduled / Recurring)
-
-
-
Status (Success / Running / Error)
-
-
Actions
-
Open destination folder (if local)
-
-
-
Executions report
Shows execution history for each task.
Status values:
-
PENDING – queued (10 min before execution)
-
RUNNING – task in progress
-
-
ERROR – failed (see error_log)
Emailing status:
-
[Send to] configuration is off
-
-
(error) mail failed (SMTP issue)
-
(denied) invalid ChronoScan user
You can also trigger the task manually from here.
How scheduled tasks are executed
Scheduled reports run in the WebServer process.
-
If WebServer is down → tasks won’t run
-
If task is PENDING, a new process can take over
-
If task is RUNNING and server stops → task ends with error
-
Tasks timeout after 10 minutes in RUNNING