fix: enable CYCLONE_SCHEDULER_AUTOSTART in docker-compose
The SFTP poller was off by default in the production container — operators had to POST /api/admin/scheduler/start manually after every restart, which they were not doing. As a result the inbound 999 / 277CA queue fell 7+ days behind in early July 2026 (scheduler.poll_count=0 in the live container since deploy). Mirrors the existing CYCLONE_BACKUP_AUTOSTART=1 entry. Note: there is a separate bug where scheduler._tick_impl's alphabetical list_inbound hangs after ~30s on mft.gainwelltechnologies.com (TCP + auth + first SFTP channel works, but the full alphabetic scan times out). The pull-inbound CLI's date-filtered path works fine — SP to follow.
This commit is contained in:
@@ -28,6 +28,11 @@ services:
|
||||
CYCLONE_BACKUP_AUTOSTART: "1"
|
||||
CYCLONE_BACKUP_INTERVAL_HOURS: "24"
|
||||
CYCLONE_BACKUP_RETENTION_DAYS: "14"
|
||||
# SP16 — SFTP polling scheduler. Without this the operator must
|
||||
# POST /api/admin/scheduler/start manually after every container
|
||||
# restart. Set on 2026-07-02 after the 7-day silent gap (see
|
||||
# git log around the SP28 merge).
|
||||
CYCLONE_SCHEDULER_AUTOSTART: "1"
|
||||
# Logging — JSON to stdout (collected by `docker logs`) and to the
|
||||
# bind-mounted file (collected by host-side logrotate).
|
||||
CYCLONE_LOG_LEVEL: "INFO"
|
||||
|
||||
Reference in New Issue
Block a user