Diagnosis: every backend restart was dispatching watch_folders.delay() unconditionally. watch_folders is an infinite-loop celery task (for changes in watch(*paths)). With CELERYD_CONCURRENCY=4 and several restarts during dev, all four worker slots ended up pinned by stale watch_folders instances, leaving zero workers free for scan_folder. The result: clicking "Scan all folders" successfully queued a task that then sat in the queue forever, the new /photos/sub folder was never walked, and the user's newly added photo never appeared. The watcher was only opportunistically useful and the user already triggers scans manually. Disabling it removes the foot-gun. Re- enabling needs: - a Redis lock so only one watcher runs at a time - or a dedicated long-running container with concurrency=1 - or a celery beat schedule with a singleton flag Until then, manual scans work. Cleared the backlog by wiping the redis broker volume so the stale watch_folders tasks are gone. Verified: post-fix, scan_folder runs in 0.12s and reports "Processed 7/7 files. Errors: 0", picking up the previously missing /photos/sub/Samuel_Colman... file. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2.3 KiB
2.3 KiB