agent-gateway: Known Failure Modes

agent-gateway receives deep-path messages from telegram-listener (HTTP POST) and routes them to rpe-context-assembler via RabbitMQ.

FAILURE MODES:

1. RabbitMQ publish failure — rpe.assemble queue not receiving messages. agent-gateway receives the HTTP call from telegram-listener but publish fails. request.module.entry appears but no request.dispatched to rpe-context-assembler.

2. RabbitMQ connection lost — channel closed mid-operation. Container may stay running but all publishes fail silently. Restart resolves.

3. Redis session corruption — stale session data causes context assembly errors. Clear RPE session keys with prefix rpe:.

4. Neo4j connection refused — graph queries fail gracefully (not fatal) but user context is missing from assembled context.

5. community-builder timeout — 3s timeout, best-effort. Failure is logged but does not block processing.

FIRST CHECKS:

• Is request.module.entry appearing from agent-gateway? If not, telegram-listener did not successfully POST.
• Is request.dispatched to rpe-context-assembler appearing? If entry present but no dispatch, check rabbitmq publish on rpe.assemble queue.
• RabbitMQ: check rpe.assemble queue depth and consumer count (should be 1: rpe-context-assembler).
• Health endpoint: http://agent-gateway:3500/health

DEPLOY TYPE: bind-mount. Changes require restart only.