Overview
The Retry Settings tab in LeadExec now distinguishes between Ping and Post behaviors:
Ping (Inbound): Only the Retry After Failure option is available. This controls automatic re-pings for buyers that fail during inbound ping scans.
Post (Inbound/Outbound): Standard retry options remain available, including Retry After Failure, Max Retry Count, and Time Between Retries. These control how Post requests are retried if delivery to a buyer fails.
Important: Ping retries only apply to inbound workflows. Web leads and outbound Ping deliveries cannot use the Ping retry feature. Post retries apply to both inbound and outbound Post deliveries.
Ping Retry Settings
Retry After Failure
Yes / No toggle.
When enabled, LeadExec automatically re-pings buyers that fail during an inbound ping.
Successful ping responses are retained and not retried.
Only available for inbound Ping workflows.
Post Retry Settings
For Post deliveries, you can configure:
Setting | Description |
Retry After Failure | Enable automatic retries for failed Post deliveries. |
Max Retry Count | Maximum number of retry attempts (recommended: 2–5, depending on lead value). |
Time Between Retries | Interval between retry attempts (recommended: 5–15 minutes, depending on urgency). |
This allows you to ensure leads are delivered reliably while avoiding system overload from continuous retry loops.
How It Works
Ping (Inbound)
Lead enters an inbound Ping/Post campaign.
LeadExec sends Ping requests to buyers.
Failed Ping responses may trigger automatic retries if enabled.
Successful Pings are retained for Post delivery and are not retried.
Post (Inbound/Outbound)
After Ping verification (if applicable), Post requests are sent.
Failed Post deliveries are retried based on configured retry settings.
Successful Post deliveries are not retried.
Best Practices
Use Ping retries to recover from temporary buyer system issues.
Configure Post retries according to lead priority:
High-value leads: 4–5 retries, 5-minute intervals.
Standard leads: 2–3 retries, 10–15-minute intervals.
Low-priority leads: 1–2 retries, 15-minute intervals.
Monitor failures to identify persistent buyer issues.
Troubleshooting
Ping retries not occurring:
Ensure Retry After Failure is enabled for Ping.
Confirm campaign is inbound Ping/Post type.
Post retries not occurring:
Verify Retry After Failure, Max Retry Count, and Time Between Retries are correctly set.
Ensure Post endpoint is accessible and responding.
Successful buyers being retried:
This is expected behavior: LeadExec only retries failed Ping/Post attempts. Successful responses are retained.
Next article: Portal Permissions Tab>