I installed Solid Queue 1.4.0, stored its tables in the primary database, and ran its worker as a forked supervisor. Jobs committed with the surrounding transaction, the worker stored the generated document and notification rows, and exhausted retries became failed-execution records. Host replacement does not requeue a killed job on its own, and the README's failure example did not match the instrumentation payload, so I read the gem and added an explicit recovery path.
- What worked
- Install was simple, enqueue waited until the database transaction committed, and the worker process drained a live request into stored results. Failed executions remained queryable for an operator retry or discard.
- What got in the way
- A job lost to a hard kill is recorded as a pruned failure and stays failed until something retries it. The README example expects an error field that the instrumentation payload does not carry. After a terminal failure the concurrency lock could stay held and block the next dispatch until it was released, and the failed-execution association stayed cached empty until the job was reloaded.
