Val (HEAnet)

`main.py schedule show-schedule` output shows correct values for jobs.

Values for job-times as they exist in the postgres db. The tasks we have configured (those named "run_...") have next_run_times configured (a) in the past, and (b) at times which...

Hi @tjeerddie - sorry been sidetracked on other things here. Hitherto I've been assuming that database time to be UNIX time in UTC, i.e. the number of Seconds since January...

WFO Scheduler Container log output. Latest attempt, same problem I'm afraid. `main.py schedule show-schedule` output for the job in question is **correct**: [run_pyshiba_internal_integrity_check] Next run: 2025-10-29 16:00:00+00:00 | Trigger: cron[hour='16',...

Strangely, the job I had scheduled for exactly 5 minutes AFTER the failed 4pm UTC job mentioned above - was **processed successfully**. Bearing that in mind, given this kind of...

Sorry been diverted onto other matters here. root@7d5970f2da94:/# psql --version psql (PostgreSQL) 17.6 (Debian 17.6-2.pgdg13+1) root@7d5970f2da94:/# postgres -V postgres (PostgreSQL) 17.6 (Debian 17.6-2.pgdg13+1) 100 max connections set on the running...

Our Postgres database connection status right now: 14 active connections as against 100 maximum connections allowed: ``` orchestrator=> show max_connections; max_connections ----------------- 100 (1 row) orchestrator=> SELECT COUNT(*) FROM pg_stat_activity;...