Scheduler Settings
The Settings → Scheduler tab holds the server-wide defaults that govern how Athena runs work in the background: the default command and deployment timeouts, how many jobs may run at once, how often dynamic collections refresh their members, how long job history, command history, and inactive agents are kept before automatic cleanup, and which mode the cron builder opens in. This page explains each setting, its default and allowed range, and how to read or change it from the console, the REST API, and PowerShell.
Reading and changing Scheduler settings requires the Admin role. See Roles & Permissions. Every change is written to the audit trail.
This page covers the server-wide scheduler defaults. To create, edit, pause, or run individual recurring jobs, see Scheduled Jobs.
Where to find it#
Open Settings → Scheduler in the console. The tab groups the defaults into three sections, each described below:
- Execution Settings — default command timeout, default deployment timeout, and maximum concurrent jobs.
- Server Tasks — agent cleanup window, command history retention, and the dynamic collection refresh interval.
- History Settings — job execution history retention and the default cron builder mode. This section holds the Save button for the whole tab.
Execution settings#
The Execution Settings section configures the default execution parameters for scheduled jobs.
| Setting | Default | Range | What it does |
|---|---|---|---|
| Default Command Timeout | 5 minutes | 1–120 minutes | The default timeout applied to command execution, in minutes. |
| Default Deployment Timeout | 120 minutes | 1–480 minutes | The default timeout for deployment tasks (2 hours by default). |
| Max Concurrent Jobs | 10 | 1–50 | The maximum number of jobs that can run simultaneously. |
Server tasks#
The Server Tasks section configures settings for the housekeeping tasks that Athena runs on the server. Two of these values are consumed by built-in cleanup tasks, and one controls how often dynamic collection membership is recalculated.
| Setting | Default | Range | What it does |
|---|---|---|---|
| Agent Cleanup Inactive Days | 30 days | 1–365 days | Days of inactivity before agents are removed by the agent-cleanup task. An agent that has not checked in for longer than this window becomes eligible for cleanup. |
| Command History Retention | 30 days | 1–365 days | Days to retain command history before it is removed by the command-cleanup task. |
| Collection Refresh Interval | 5 minutes | 0–1440 minutes | How often Athena automatically re-evaluates the membership of dynamic
collections. Set to 0 to disable automatic
refresh entirely. |
Setting Collection Refresh Interval to 0 disables the
automatic background refresh. Dynamic collections then only recalculate when triggered
manually. A very short interval refreshes membership sooner at the cost of more frequent
recalculation — 5 minutes is the shipped default.
History settings#
The History Settings section configures job execution history retention and the default mode the cron builder opens in. The tab's Save button lives in this section and commits every change made across all three sections.
| Setting | Default | Choices / Range | What it does |
|---|---|---|---|
| History Retention | 30 days | 1–365 days | How long scheduled-job execution history is retained. |
| Cron Builder Default Mode | Visual Builder | Visual Builder, Text Input | Which mode the schedule builder opens in when you create or edit a recurring job: the point-and-click Visual Builder or direct Text Input of a cron expression. |
REST API#
The same settings are available over the JWT-authenticated REST API on
port 8443. Send the bearer token as
Authorization: Bearer <token>; both endpoints require the Admin role.
| Endpoint | Role | Purpose |
|---|---|---|
GET api/settings/scheduler | Admin | Read the current scheduler settings. |
PUT api/settings/scheduler | Admin | Update the scheduler settings. Send the full settings object. |
GET api/settings | Admin | Read every settings category at once, including Scheduler. |
# Read current scheduler settings
curl -k -H "Authorization: Bearer <token>" \
https://athena.example.com:8443/api/settings/scheduler
# Update: 10-minute command timeout, 3-hour deployment timeout,
# keep job history 60 days, refresh collections every 10 minutes
curl -k -X PUT -H "Authorization: Bearer <token>" \
-H "Content-Type: application/json" \
-d '{
"defaultCommandTimeoutMinutes": 10,
"defaultDeploymentTimeoutMinutes": 180,
"maxConcurrentJobs": 10,
"historyRetentionDays": 60,
"cleanupInactiveDays": 30,
"collectionRefreshIntervalMinutes": 10,
"commandRetentionDays": 30,
"cronBuilderMode": "Visual"
}' \
https://athena.example.com:8443/api/settings/scheduler
Send the object you read back from GET with the fields you want to change — the
update replaces the scheduler settings with the values you supply.
PowerShell#
The Athena PowerShell module reads and writes the scheduler
settings with Get-AthenaSettings and Set-AthenaSettings using the
Scheduler category. Sign in with
Connect-Athena as an Admin first.
# Connect as an Admin
Connect-Athena -Server "athena.contoso.com"
# Read the current scheduler settings
$scheduler = Get-AthenaSettings -Category Scheduler
$scheduler.MaxConcurrentJobs
$scheduler.CollectionRefreshIntervalMinutes
# Keep job history for 60 days and refresh collections every 10 minutes
$scheduler.HistoryRetentionDays = 60
$scheduler.CollectionRefreshIntervalMinutes = 10
Set-AthenaSettings -Category Scheduler -Settings $scheduler
# Disable automatic dynamic-collection refresh
$scheduler.CollectionRefreshIntervalMinutes = 0
Set-AthenaSettings -Category Scheduler -Settings $scheduler
Set-AthenaSettings supports -WhatIf/-Confirm, so you can
preview a change or gate it in a script.
Auditing#
Every change to the scheduler settings is written to the audit trail as a Scheduler settings change, recording the acting user, their IP address, and which values changed — for example a new deployment timeout or a change to the collection refresh interval. This gives you a complete record of who adjusted the background-work defaults and when.
Related#
- Scheduled Jobs — create and manage the recurring jobs these defaults apply to.
- Collections — dynamic collections refreshed on the interval set here.
- Software Deployment — deployments that use the default deployment timeout.
- Retiring & Removing Agents — how the inactive-agent cleanup window fits into agent lifecycle.
- General Settings — console-wide preferences on a neighbouring Settings tab.
- Roles & Permissions — the roles that govern who can change these settings.