Marc-André Bombeck f18e6ed34b fix(backup): notice a backup run the process died under, and take its account last ...

A weekly or nightly backup job whose process died (a restart, a
container out of memory) stayed active until its two- or four-hour
expiry, and its retry walked the accounts in the same order: the account
that killed it has the oldest copy, so it led again, and every account
after it went without a copy for as long as that record stayed too
large.

Both passes now send with a five-minute pg-boss heartbeat, so a dead run
fails within minutes and its retry picks it up. Each pass records when it
started and finished every account (backup_pass_attempts, migration
0373); an account whose last attempt never finished goes behind all the
others. The backups page shows when the run in progress started and names
an account a run died under, for the weekly and the off-host card, and a
heartbeat timeout reads as what it means.

2026-10-04 15:56:56 +02:00

..

analytics.ts

feat(analytics): replace health score with reference composite

2026-07-28 21:10:15 +02:00

backups.ts

fix(backup): notice a backup run the process died under, and take its account last

2026-10-04 15:56:56 +02:00