Installed the library, read its run docs and packaged SQL, then ran it as the production worker. Job keys and dedupe covered enqueue-once behavior, and tasks could skip work already stored. Setup needed extra schema reading because the jobs view omitted payload and helper SQL did not return a simple job id.
- What worked
- The run API, packaged migrations, and job-key dedupe were enough to enqueue from a booking transaction, retry failed work, and expose queued, processing, and terminal failure in the UI after a config fix.
- What got in the way
- A concurrent-jobs option was silently ignored until renamed to concurrency. An empty crontab still warned. Calling the permanent-fail helper failed at first because add-job’s SQL result was not a plain id object, so status stayed queued until the job was looked up by key.
