Radiator Server Documentation — v10.34.1

Emission

Log level: TRACE

Per-request tracing: Yes

Logged when an HTTP backend schedules another attempt after a configured retry condition. The backend field identifies the dependency, and operation identifies the query or protocol phase. The attempt field identifies the upcoming attempt, and retries_remaining excludes that attempt. The max_attempts field identifies the total attempt limit. The delay_ms field contains the jittered wait, and reason identifies the triggering outcome. HTTP response retries include status_code. Request failures include the structured error.

Use reason to identify the cause. For timeout, check dependency latency and capacity. For request-error, check the structured network or transport error. For status-code, check the dependency behavior for the reported status_code.

Compare backend Retries with Requests, Timeouts, and Errors. Correct dependency, network, or traffic problems before changing the backend's retry configuration.