Understanding Awaiting Callback in Email Enrichment Tools
What does it mean when a "Find Email" Email Enrichment provider is stuck on "Awaiting Callback" in its cell?
What does it mean when a "Find Email" Email Enrichment provider is stuck on "Awaiting Callback" in its cell?
When an email enrichment provider shows "Awaiting Callback" in its cell, this indicates the provider is currently processing your request and hasn't returned a result yet. During waterfall enrichment, Clay dynamically moves through providers - if a provider finds a valid email, the process stops for that contact, and if no email is found, credits are refunded and Clay moves to the next provider. Which specific email provider is showing "Awaiting Callback" and how long has it been in this status?
Wiza, several minutes
If Wiza has been showing "Awaiting Callback" for several minutes, this typically indicates a processing delay. This can happen due to API limits or high request volumes. During waterfall enrichment, providers may take time to process requests. If no email is found after processing, credits are refunded and Clay moves to the next provider. Try refreshing your table or waiting a bit longer. If the issue persists beyond 10-15 minutes, you may want to request human assistance by clicking "Talk to a person" for further troubleshooting.
I'm running a formula based on the output of the Find Work Email enrichment and the formula is messed up because the Wiza status is stuck on awaiting callback
When Wiza is stuck on "Awaiting Callback," your formula can't access the email output, causing issues. To resolve this, go to your waterfall column and use "Run all rows that haven't run or have errors" to re-run the failed Wiza attempts. This will process only the entries that weren't completed, avoiding duplicate runs on successful searches. Once Wiza completes processing, your formula should work properly with the email output.
I tried re-running the Wiza enrichment and it still returns "Awaiting Callback"
If Wiza continues showing "Awaiting Callback" after re-running, this may indicate a persistent API issue or credit shortage. Try using "Run all rows that haven't run or have errors" from your waterfall column to specifically target the failed attempts. If the issue persists, you can temporarily skip Wiza by adjusting your waterfall order or removing it temporarily to let other providers process while the issue resolves.