Keep the job thread alive after an error of the queue

An error outside a job, such as a full disk, stopped the thread, and no job ran until a restart. The health check now answers 503 when a job thread stopped.
2026-10-02 23:37:33 +02:00
parent c0504135b2
commit 81efc03b75
4 changed files with 80 additions and 15 deletions
@@ -426,6 +426,9 @@ After a restart, the waiting jobs run. A job that was running starts again at th
 queue, and skips the chapters that it stored. If Bindery stops during the same job three times, the
 job fails.

+If a job thread stops, `/api/health` answers 503, so the container shows as unhealthy. Restart
+Bindery to start the thread again.
+
 ### Backups

 Once a day, Bindery copies its database and `personal.ini` to `/config/backups`, and keeps the