Automated Retry

Feature Snapshot

Summary:
Automated Retry is a LeadConduit feature that automatically reattempts the delivery of leads when temporary errors occur. By queuing leads that encountered transient issues during their initial delivery and reprocessing them using an exponential backoff algorithm, this feature helps ensure that leads ultimately reach their intended recipient even if early attempts fail.

Key Benefits:

• Minimizes manual re-submission of leads
• Increases overall lead delivery success in the face of temporary outages
• Uses a smart exponential backoff cadence to avoid overloading recipient systems
• Provides clear tracking of retry outcomes for operational insight

Typical Use Cases:

• Reattempting delivery to systems that experience intermittent downtime (e.g., 500-series errors)
• Flows where small, temporary disruptions could otherwise result in lost leads
• High-reliability lead delivery scenarios requiring automated recovery from transient failures

How the Automated Retry works?

When a recipient step encounters a transient error, the lead is automatically placed in a retry queue. The feature then reattempts delivery of the lead up to a predetermined maximum number of times (default set to 100 retries in beta). The retry process employs an exponential backoff cadence – starting with a 10-second delay and gradually increasing to a maximum of 15 minutes – to balance prompt lead resubmission with the need to avoid overwhelming the recipient system. Outcomes of these retry attempts are tracked as Success, Failed, or Error, allowing you to monitor and adjust your retry strategy based on observed performance.

Step‑by‑Step Instructions

1. Enable Automated Retry on Your Recipient Step:
   In your LeadConduit flow editor, navigate to the recipient step where delivery may encounter transient issues. Locate and enable the Automated Retry option.

2. Save and Activate Your Flow:
   After confirming the settings, save your flow changes and activate the flow so that Automated Retry becomes effective immediately.

3. Monitor Automated Retry Events:
   Use the Automated Retry events view within your LeadConduit dashboard to verify that failed deliveries are being retried appropriately and to monitor final outcomes of each retry attempt.

Expected Result:
A lead that initially encounters a transient error is enqueued for retry, and subsequent delivery attempts occur using the defined backoff cadence. Ultimately, the lead’s outcome is recorded as Success if delivered, Failed if all retries are exhausted, or Error if a terminal error occurs.

Validation & Monitoring (optional)

• Test the Setup:
  Submit a test lead to a recipient step configured with Automated Retry while simulating a temporary error (for example, a 500-series HTTP response). Verify that the lead is placed in the retry queue and that, once the recipient system recovers, the lead is successfully delivered.

• Where to Monitor?:
  Monitor retry activity through LeadConduit’s Automated Retry events type view, available in Lead Events or specific Reporting. Look for metrics such as the number of retry attempts, the delay intervals between attempts, and the final status of the lead delivery.

Best Practices

• Use Automated Retry exclusively for transient errors such as temporary outages or intermittent 500-series failures; do not enable it for permanent validation problems.
• Regularly review Automated Retry event logs to ensure that retry behavior meets your business objectives.
• Test the configuration in a staging environment before rolling it out in production to confirm the behavior aligns with expected patterns and to mitigate potential disruptions.

Troubleshooting

Frequently Asked Questions (FAQ)

What types of errors trigger Automated Retry?

Automated Retry is designed to capture temporary errors such as server downtime, 500-series responses, or intermittent connectivity issues. It does not trigger for errors resulting from invalid lead data.

How does Automated Retry affect my overall flow?

The Automated Retry process operates independently in the background. While a lead is queued for retry, the primary flow continues processing, and the lead’s original data remains intact.

Can I monitor retry events in real time?

Yes, retry events and their outcomes are visible via LeadConduit’s Automated Retry events view from the Lead Events page, allowing you to monitor their status in near real time.

What happens if all retry attempts fail?

If all configured retry attempts are exhausted without a success, the lead’s final outcome is marked as “Failed” or “Error.” This outcome is recorded without altering the original lead data, ensuring that you have a complete audit trail.

Glossary

• automated-retry-configuration.png200 KB