You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Redis lost connection does not seem to get re-created #2072
For anyone still hitting this: the root cause is MutexOwner returning an invalid gen_statem value on Redis errors, which crashes it and takes down all consumers via the :one_for_all supervisor. A fix (retry with capped exponential backoff, re-acquire on recovery) was submitted as #2131 but upstream appears unmaintained since Feb 2026 — it's now merged and released in the maintained fork: https://github.com/triptechtravel/sequin (v0.14.6-tt2, ghcr.io/triptechtravel/sequin:v0.14.6-tt2).
Activity
Sh4d1 commentedon Sep 10, 2025
@RTLS is this expected ? 🤔
Fix Redis connection loss not auto-reconnecting
Fix Redis connection loss not auto-reconnecting
fix: MutexOwner retries on transient Redis errors instead of crashing
isaacrowntree commentedon Jun 12, 2026
For anyone still hitting this: the root cause is MutexOwner returning an invalid gen_statem value on Redis errors, which crashes it and takes down all consumers via the :one_for_all supervisor. A fix (retry with capped exponential backoff, re-acquire on recovery) was submitted as #2131 but upstream appears unmaintained since Feb 2026 — it's now merged and released in the maintained fork: https://github.com/triptechtravel/sequin (v0.14.6-tt2,
ghcr.io/triptechtravel/sequin:v0.14.6-tt2).