​

Troubleshoot a delivery

When a lead is visible but no buyer receives it, check the flow in order. Fix the first failing layer instead of changing several settings at once.

​

1. Did ingest create the expected records?

Open Records → Persons and Records → Interests. Confirm:

• the person exists
• the correct interest and product exist
• required contact and consent data are present
• qualification fields contain the expected values
• the source did not report a rejected duplicate or mapping error

If fields are wrong, fix the source or mapping before investigating delivery.

​

2. Is the interest in the intended channel?

Open the channel and search for the person, lead ID, or external ID. If it is missing:

• confirm the source targets this channel
• confirm the product belongs to the channel’s scope
• check whether the lead was sent to a Company list instead
• inspect the source’s test/live mode

​

3. Is the interest ready for routing?

Inspect the request, quality, and routing columns. An interest can be blocked by:

• missing required values
• pending or failed quality checks
• duplicate rules
• source filters or caps
• routing readiness not being set

Routing-ready means “eligible for evaluation,” not “guaranteed to be delivered.”

​

4. Is at least one buyer eligible?

Open the channel Output area and check:

• the pool is linked and active
• the buyer is active
• the buyer supports the product
• field criteria match the interest values
• buyer capacity remains
• exclusive or multi slots remain
• the buyer has not already received this interest

Open the buyer or eligibility explanation to identify the exact failed rule.

​

5. Is the delivery method configured?

Confirm the buyer has a usable destination:

• webhook URL and authentication
• Connect endpoint and active partnership
• required field mapping
• any integration-specific credentials

Run a manual test delivery. If it creates a transaction but the partner receives nothing, inspect the outbound request and buyer response.

​

6. Is Delivery 1.0 allowed to deliver?

If manual delivery succeeds but automated delivery does not, confirm:

• Delivery 1.0 is enabled for the channel
• automated delivery is enabled for the buyer
• the plan includes the required capability
• AI usage budget is available
• no channel or buyer override blocks delivery

​

7. Read Activity

The Activity tab is the source of truth for what Airlead evaluated. Look for:

• ingest events
• matching and eligibility results
• delivery attempts
• partner response errors
• retries
• block reasons

Avoid repeatedly triggering delivery before understanding the current transaction history.

​

Symptom guide

​

Still unresolved?

Check the FAQ first. Then collect these details before contacting support:

• workspace and channel name
• lead, interest, and external ID
• source and buyer name
• expected result
• first visible block reason
• transaction ID, if one exists
• approximate event time

Next: Understand channels · Prevent duplicates · Developer errors and retries