Resilience: hbf-event-publisher

Error handling and retry patterns for this service. Platform-wide patterns: docs/architecture/resilience.md

HTTP Retry

• Library: got (v11.8.5)
• Attempts: 1 (no retry configured)
• Backoff: N/A
• On failure: HTTPError caught, logged, and rethrown

Queue Retry (if applicable)

N/A

Timeouts

Call	Timeout	Configured in
All HTTP calls	Not configured	N/A

Circuit Breakers

None.

Fallback Strategy

Failure scenario	Behaviour	User impact
Any HTTP error	Error propagated to caller	Event delivery fails, no fallback

Known Gaps

• No retry on any HTTP call (single failure causes immediate propagation).
• No timeout configured (requests may hang indefinitely).
• Health endpoint: the health() method uses @Get() with no path argument, mapping to GET / (root), not GET /health. It is effectively unreachable as a separate route.
• No circuit breaker for downstream services.