# Self-Healing CI: Recovering a Message Queue Connection Drop

> A step that fails because a message-queue connection dropped is a transient transport blip, not a broker outage. See the manual fix and how self-healing CI reconnects and retries.

Source: https://latchkey.dev/learn/self-healing-ci/self-healing-message-queue-connection-drop  
Updated: 2026-06-26

A step that loses its connection to a message broker hit a transient transport blip or a broker rebalance, not a permanent outage -- reconnecting and retrying clears it.

## What makes a failure safely retryable

Automatic retry is only correct for failures that are genuinely transient. Retrying a deterministic failure wastes minutes and hides a real defect, so the classification matters more than the retry mechanism.

- Safe to retry: network timeouts, registry 5xx, transient DNS failures, a service container that was not ready, a spot instance reclaimed mid-run.
- Not safe to retry: assertion failures, compile errors, lint violations, anything that fails identically on every attempt.
- Ambiguous, and worth investigating rather than retrying: out-of-memory kills, disk exhaustion, and flaky tests. These repeat under load and a retry only hides the trend.
- Always record that a retry happened. A pipeline that silently retries is a pipeline whose real failure rate you do not know.

## FAQ

### What causes Self-Healing CI: recovering a message queue connection drop?

A step that publishes to or consumes from a message queue (AMQP, Kafka, etc.) fails because the broker connection dropped -- a reset, a heartbeat miss, or a brief rebalance. The broker and credentials are fine; the connection was severed transiently. A human re-runs and the step reconnects and completes unchanged.

### How do I fix Self-Healing CI: recovering a message queue connection drop manually?

[object Object]

### Can Self-Healing CI: recovering a message queue connection drop be fixed automatically?

A dropped broker connection has a recognizable transient signature -- a reset or rebalance rather than an auth or routing error -- and the safe response is to reconnect and retry. A self-healing CI pipeline detects the connection drop, retries with backoff after reconnecting, and only escalates if the broker is genuinely unreachable,

---

Latchkey runs CI/CD that repairs its own failures. Agent entry points: https://latchkey.dev/agent.txt, https://latchkey.dev/openapi.json, https://latchkey.dev/llms.txt