Chronos Scheduler changelog
Release notes
0.3.4
Released: November 10, 2026
-
Added support for Core Hub disaster recovery pairs. With
GS_DR_CONTROL_URLset to the control port of its own Core Hub, Chronos opens its database only while that Core Hub is the serving active site: on the standby site it waits, so schedules never run on both sites, and when its Core Hub stops serving it stops and starts waiting again. The guided setup of the Control Plane sets the variable for you. Without it, nothing changes. See Set up a disaster recovery pair; -
While it holds its database, Chronos keeps a heartbeat file (
.dr-chronos-heartbeat) in its data folder, so that Core Hub waits for Chronos to close the database before a switchover or a promotion; -
A Chronos waiting on a standby site reports
healthyto the container health check on the Linux and Windows images, so Docker Swarm does not restart it in a loop; -
The certificate of the Core Hub control port is checked unless
SSL_SKIP_VERIFYistrue, like every other call Chronos makes to Core Hub;
0.3.3
Released: November 4, 2026
-
Fixed requests that Traefik routes over a Podman network being refused with
403: the check of the caller accepted only127.0.0.1,::1,172.*and192.168.*, while Podman’s default networks are10.88.0.0/16and10.89.x.0/24. Chronos now accepts loopback, private-network (RFC 1918:10.0.0.0/8,172.16.0.0/12,192.168.0.0/16), link-local and IPv6 unique-local callers. A172.*address outside172.16.0.0/12, which is a public address, is no longer accepted. See Gluesync on Podman; -
New installs on the Linux images run Chronos as user
1017(thegluesyncuser of Core Hub) instead of root. Existing installs keep running as root: at the first start the entrypoint sees that/app/dataalready holds files and recordsrootin/app/data/.chronos-run-as; an empty folder means a new install and recordsgluesync. The choice never changes on restarts or updates.CHRONOS_RUN_AS=gluesyncmoves an existing install to user1017(its data and logs are given to that user once),CHRONOS_RUN_AS=rootkeeps root; -
The Linux images now start when the container does not run as root, as under Podman rootless or Kubernetes
runAsUser: Chronos runs as that user and says so in the log when it cannot write its folders; -
Fixed an issue on installations first created by an older Chronos release where creating a setting failed with
400(NOT NULL constraint failed: settings.created_at), while changing an existing setting worked. Thesettingstable is repaired on the first start of 0.3.3, keeping every setting;
0.3.2
Released: October 28, 2026
-
Fixed an issue where Chronos stopped responding at the daylight saving time change in autumn: a cron schedule computing its next run inside the repeated hour kept the scheduler busy forever, so no schedule ran and the API did not answer. Schedules also no longer wait an hour too long across the spring change (GSSD-1457);
-
Runs missed while Chronos was stopped are now run once when it starts again, if they are at most one hour late. A missed maintenance exit (
pipeline_exit_maintenance) is always run, however late, so a pipeline is never left in maintenance; a warning in the log says how late it was (GSSD-1457); -
Fixed the next run time of schedules in a timezone other than UTC: it was stored as local time without its offset and read back as UTC, so after a restart missed runs could be skipped and the API showed a next run off by the timezone offset. Next run times are now stored in UTC; existing schedules are converted once, automatically, on the first start of 0.3.2 (GSSD-1457);
-
Added
GET /health(no authentication) and a container health check on the Linux and Windows images, so a Chronos that stops responding is markedunhealthyby Docker. A Core Hub that cannot be reached is reported asdegraded; -
Added the Core Hub backup task type (
corehub_backup), used by Core Hub to keep its backup schedule in Chronos; -
Schedules accept an optional
timezone_name(an IANA name such asEurope/Rome) to run in their own timezone instead of the global timezone setting; an unknown name is refused with422; -
Fixed requests with invalid fields answering
500instead of422, and/api/openapi.json,/api/docsand/api/redocanswering500; -
Added Linux images for x86-64 CPUs without x86-64-v2 support, tagged
<version>-debian(andlatest-debian,beta-debian). The default images stop on such CPUs withFatal glibc error: CPU does not support x86-64-v2. Gluesync Control and the installers choose the-debianimage on those CPUs automatically; see Installers changelog; -
Updated the base images and their packages to fix reported vulnerabilities;
0.3.1
Released: October 21, 2026
-
Fixed cron schedules that set both the day of the month and the day of the week: they now run when either field matches, as standard cron does. Before, they ran only on days that matched both, so for example
50 11 20 8 4did not run on August 20; -
Added the
day_orschedule setting.true, the default for new schedules, runs when either field matches;falseruns only when both match, for example on the first Saturday of the month with0 9 1-7 * 6. It has no effect when either field is*, and it can be changed on an existing schedule. See Day of the month and day of the week; -
In the Gluesync 2.3.0.3 UI,
day_oris the Run when either the day of month or the day of week matches checkbox in the CRON tab, and the schedules list marks schedules that need both days to match; -
Schedules created before this version are set to
day_or: falseon upgrade, so they keep running on the same days as before; their next run time is recalculated;
0.3.0
Released: October 13, 2026
-
Added the AI agent run task type (
ai_agent_run) for schedules, chained events, platform events, and webhook-triggered events; -
AI agent run tasks execute a published agent by its required
agent_alias, with optionalagent_version;pipeline_idis optional; -
Added allow-listed scalar payload interpolation for
prompt_template,agent_input, andidempotency_key; -
Added a 64 KiB limit for trigger fire request bodies and loop protection for AI run platform events;
0.2.6
Released: October 12, 2026
-
Restores the 0.2.4 fixes that 0.2.5 did not include: the SDK token refresh on 401 now performs a fresh login handshake, and the periodic Core Hub connection health check (
CHRONOS_HEALTH_CHECK_ENABLED,CHRONOS_HEALTH_CHECK_INTERVAL_SECONDS,CHRONOS_HEALTH_CHECK_TIMEOUT_SECONDS) is back; -
Fixed an issue on the Windows image and Python package installations where the first start of a new installation, or of an upgrade from 0.1.x, created the
chained_job_eventstable without thewebhook_timeout_secondscolumn, so listing jobs failed until Chronos was restarted; -
Fixed an issue on the Windows image and Python package installations where the
trigger_flowstable was missing theroutingcolumn on a new installation or after an upgrade from 0.2.0, 0.2.1 or 0.2.2, so trigger flow requests failed; -
Databases left in either state are repaired on the first start of 0.2.6, with no manual steps;
-
migrations/run_migrations.shnow runs the same migrations, in the same order, as Chronos does at startup;
0.2.5
Released: September 28, 2026
-
Now the scheduled snapshots always reset the migration checkpoint;
0.2.4
Released: September 14, 2026
-
Fixed a bug where the SDK token refresh on 401 would reuse the same stale token instead of performing a fresh login handshake — the SDK client is now properly disconnected and recreated on reconnect;
-
Added a periodic Core Hub connection health check that calls
GET /authentication/meevery 5 minutes (configurable) and automatically triggers a force-reconnect when the token is rejected or Core Hub is unreachable; -
Added
CHRONOS_HEALTH_CHECK_ENABLED,CHRONOS_HEALTH_CHECK_INTERVAL_SECONDS, andCHRONOS_HEALTH_CHECK_TIMEOUT_SECONDSenvironment variables; -
Added a warning log when the refreshed token is identical to the rejected token, making stale-connection issues easier to diagnose;
0.2.3
Released: September 7, 2026
-
Added the Query Studio action type (
query_studio) for schedules, chained events, platform events, and webhook-triggered events; -
Query Studio tasks can run custom SQL or a saved query against a selected pipeline agent; execution goes through CoreHub Query Studio (120s timeout) and is never placed on the crontab command line;
-
Writable Query Studio execution requires an explicit
query_read_onlyopt-in; -
Fixed job creation failing with HTTP 500 when the UI sent
query_read_only: nullfor non-Query-Studio jobs (null is now treated as read-only); -
Added origin vs broadcast routing for platform-event trigger flows — origin loops the action back to the event source, broadcast fans out as before; table reorg, truncate, and DDL default to origin, cluster-wide events default to broadcast;
-
Pause-before-redo now treats Warning as settled (alongside Hold and Error), so redo proceeds when entities report
errorState.severity=WARNING;
0.2.2
Released: August 21, 2026
-
Redo operations (entity, pipeline, group) now pause CoreHub (stop / stop-group) and wait until every affected entity is Hold before issuing the redo; no more fixed sleep;
-
If the pause fails or Hold is not reached before timeout, the redo is aborted;
0.2.1
Released: August 18, 2026
-
Fixed an issue where the
trigger_flowstable was created without theplatform_eventcolumn on a fresh database, causingGET /api/triggers/to return a 500 error at container bootstrap time;
0.2.0
Released: July 27, 2026
-
Breaking change: this version is only compatible with Core Hub 2.2.10+ onwards;
-
Added chained events with sync/async execution modes and configurable webhook timeouts;
-
Added webhook triggers for external events;
-
Added platform-bound events via persistent webhook registration in CoreHub with retry and filter support;
-
All API endpoints are now secured with JWT authentication via CoreHub introspection;
-
Added role-based access control (SUPER_ADMIN, MANAGER, VIEWER, EXTERNAL_MODULE);
-
Optimized job loading with batch queries and cached timezone resolution;
0.1.57
Released: July 18, 2026
-
GSSD-1195: Chronos now automatically refreshes its own auth token after core hub’s session expires;
0.1.56
Released: June 17, 2026
-
Swapped Linux base image from Debian to Chainguard/Wolfi for improved security and smaller footprint;
0.1.54
Released: June 3, 2026
-
GSSD-976: Fixed an issue with the scheduler not firing Snapshot events over Groups;
0.1.53
Released: June 1, 2026
-
PythonSDK version bump;
-
Improved reconnect to Core Hub reliability;
-
Security patches;
0.1.50
Released: April 27, 2026
-
GSSD-870: Fixed the scheduler event loop getting stuck if multiple concurrent schedules are fired;
0.1.49
Released: April 10, 2026
-
Improved artifacts management for offline mode in Windows environments;
0.1.43
Released: February 13, 2026
-
Fixed a regression caused by too strict user permissions in Linux containers;
0.1.41
Released: February 10, 2026
-
GSSD-608: System time was winning over the user-selected timezone;
-
Docker image now uses a unprivileged user for security reasons;
0.1.34
Released: November 11, 2025
-
Moved tawards new /opt/gluesync/shared volume mount (while maintaining backward compatibility);
0.1.33
Released: November 7, 2025
-
Updated Python SDK to the latest version 0.11;
-
Re-send license headers at every reconnection to the Core Hub;
0.1.32
Released: October 26, 2025
-
When setting an hardcoded CORE_HUB_URL in the environment variables, Chronos will still attempt to retry connection to the Core Hub with exponential backoff;
-
GS SDK updated to the latest version 0.11;
0.1.30
Released: October 23, 2025
-
Major refactor an env vars management to support Nanoserver images and Windows containers, especially legacy 2019;
-
Libs upgrades;
0.1.27
Released: September 24, 2025
-
Fixed an issue that was causing Chronos to crash if the Core Hub APIs where responding 404;
-
Updated websockets library to use the latest version;
0.1.26
Released: September 22, 2025
-
Auto set targeted objects in a scheduled jobs to STOP before executing a Snapshot task;
0.1.24
Released: September 18, 2025
-
Fixed an issue that could prevent the Scheduler icon from being displayed in the Gluesync UI;
0.1.23
Released: September 17, 2025
-
GSSD-338: fixed an issue that could cause one-shot-snapshots targeting a group to fail;
-
Official support for Windows-based containers;
0.1.22
Released: September 16, 2025
-
GSPRJ-1123: fixed a bug that was causing last_run, next_run and start_time to work on different timezones formats;
0.1.21
Released: September 15, 2025
-
CORE_HUB_URL has now become GLUESYNC_HOST environment variable to be consistent with other modules;
0.1.20
Released: September 15, 2025
-
Fixed an issue that could cause scheduled jobs with "snaphost only mode" to trying to run a snapshot + cdc instead;
0.1.15
Released: August 22, 2025
-
Fixed an issue that could cause the scheduler to crash if after several attempts to connect to the Core Hub it fails to schedule a task;
0.1.14
Released: August 8, 2025
-
Chronos now provides evidence whether a job has been scheduled via a Cron-like expression or a human readable format;
0.1.13
Released: July 31, 2025
-
Fixed an issue that could cause the scheduler to continue using an outdated Core Hub URL after CoreHub’s restart;
-
Fixed an issue that could cause the scheduler to continue using an outdated Core Hub API token after CoreHub’s restart;
-
Improved error handling, now properly forwarded to API and UI in case of a schedule failure;
-
Enhanced logging for better debugging experience;
-
Minor bugfixes and improvements.