The Wire · Showcase
SOLID_QUEUE ADDS CONFIG VALIDATION BEFORE STARTUP
By RepoJournal · Filed · About Rails
Solid Queue ships a critical safety check that catches broken recurring.yml before your supervisor silently exits with no workers running.
The new `bin/jobs check` command [1] validates your Solid Queue configuration before the supervisor boots, solving a nasty class of production failures where typos in cron syntax cause the process to exit cleanly without error logging. Previously [2], a malformed recurring.yml would print to stdout nobody was listening to, then exit successfully, leaving you wondering why scheduled jobs never ran. This works as both a CLI command and a `solid_queue:check` rake task, and intelligently skips database checks on CI where credentials aren't available. In parallel, Solid Cable v4.0.2 shipped a fix [3] that resets the retry counter on each successful poll [4], preventing unnecessary backoff accumulation across network glitches. On the Rails core side, a regression test landed [5] for `config.action_dispatch.default_headers` set in initializers, guarding against 8.x breakage where the timing of config propagation was broken. Documentation cleanup continues across the main Rails repo [6], sweeping typos from guides and API docs.
Action items
- → Run `bin/jobs check` now to validate your recurring.yml before next deploy rails/solid_queue [immediate]
- → Upgrade Solid Cable to v4.0.2 for retry counter fix rails/solid_cable [plan]
- → If on Rails 8.x, verify default_headers in initializers are still working rails/rails [monitor]
References
- [1] add bin/jobs check to validate config before starting ↗ rails/solid_queue
- [2] add bin/jobs check to validate config before starting rails/solid_queue
- [3] v4.0.2 ↗ rails/solid_cable
- [4] Reset retry counter on each successful poll ↗ rails/solid_cable
- [5] Test that config.action_dispatch.default_headers set in an initializer is applied ↗ rails/rails
- [6] Fix typos and inconsistencies in documentation ↗ rails/rails
