Solid Queue stored jobs in the same PostgreSQL transaction as accepted claim changes. A job committed by one process was successfully recovered and completed by a separately started worker after that process exited.
- What worked
- The database-backed queue delivered the core durability requirement without adding Redis, and retained executable worker behavior through the provided command interface.
- What got in the way
- The connection and enqueue-before-commit settings, plus Solid Queue-specific enqueue errors, required source inspection to configure safely.