# How Volume Spikes Affect Recovery When you get a big surge in failed payments, recovery rates can look temporarily worse even though everything's working fine. Recovery takes time, so when a large batch of failures hits all at once, Redux needs time to work through them. ### **What's really happening:** #### **1. Both baseline and Redux recovery take time** A sudden jump in failures immediately increases your total failure count, but recoveries happen over several days or weeks. This temporarily pushes recovery rates down even though nothing's actually wrong. #### **2. Performance stabilizes as retries run** As Redux processes the spike, classifies each failure, and times the retries properly, recovered payments start catching up. Your performance naturally moves back to normal as the spike gets absorbed. #### **3. More volume often means more opportunity** Bigger batches usually include more recoverable failures. Once the system works through them, you often see higher lift because there's simply more recoverable revenue to capture. #### **4. Spikes aren't a performance problem** They're just a timing mismatch between when failures happen (instantly) and when recoveries can logically complete (over several days). ### **The bottom line:** Volume spikes temporarily make recovery rates look worse, then normalize as retries complete. They don't hurt actual performance and often lead to higher total revenue recovered once everything's processed. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.reduxpayments.com/recovery-performance/how-volume-spikes-affect-recovery.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.