Maurice a72497b3c4 fix(server): trace a cron tick lost to another process as skipped ...

A tick whose lease another process held returned from runLeased without
running, and traceEntry still wrote `cron <name> ok`, so both processes
logged the tick as run and the per-tick line could not tell which
replica did the work. runLeased now says whether the tick ran, and
traceEntry takes a `skipped` option that logs such a call at debug as
`cron <name> skipped <ms>: lease held by another process`.

Taking the lease is two statements (make sure the row exists, then the
conditional UPDATE that decides the race), so it now runs inside
UnitOfWork.transactional like every other multi-statement write.

2026-10-08 18:40:37 +02:00

..

cron-registrar.service.ts

fix(server): trace a cron tick lost to another process as skipped

2026-10-08 18:40:37 +02:00

scheduling.module.ts

feat(server): add the schedule wiring

2026-08-10 21:22:13 +02:00