Moleculer Redis transporter interaction: default retry limit handling

The goal is to clarify how Moleculer’s Redis transporter behaves when an action throws an error and no custom retries is defined. The framework’s documentation states that the default retry policy is indefinite, which may lead to continuous re‑delivery attempts and uncertain back‑pressure semantics under sustained failure conditions.

Constraints include the absence of a user‑specified retry limit, reliance on the transporter’s internal retry loop, and the potential for resource exhaustion if failures persist. Understanding whether the transporter applies any implicit delay, circuit‑breaker interaction, or termination condition is essential for designing resilient services.

Does Moleculer continue retrying the failed action indefinitely until the process is stopped?
What back‑pressure or delay mechanisms, if any, are applied during continuous retries?
How can developers observe or constrain this retry behavior without modifying each action’s options?