Hey team, my waterfall Zerobounce validation is showing errors, can you take a look? Some of the rows went through fine but some kept coming back in error: Here's the table
It's normal for some rows to show errors while others go through fine in a Zerobounce validation waterfall. This happens because: 1. The waterfall continues running even after finding an email if it fails the validation check. 2. Different email addresses may have different validation results (valid, invalid, catch-all, etc.). To resolve this: 1. Unhide the validation columns to see detailed results for each email. 2. Consider adjusting the "Safe to Send" setting if you're seeing many catch-all emails. 3. Review the specific error messages for insights into why certain emails failed validation. If you need more help, request human assistance by clicking on "Talk to a person" in this chat.
what's Zerobounce API rate limit
We don't have specific information about Zerobounce API rate limits for email validation in Clay. Our integration with Zerobounce allows you to validate work emails to ensure they're safe, reducing bounces and improving deliverability. You can use either the Clay-managed Zerobounce account or bring your own API key. To get more details about API rate limits, could you clarify if you're using the Clay-managed Zerobounce account or your own API key?
Hey there! Sorry about this. We're currently investigating this error with the provider and will get back with an update🙏🏾. Truly sorry for the inconvenience.
Hey there! Happy to report that the issue causing 429 errors with ZeroBounce has been resolved. We also added credits for all affected rows. Try a quick refresh and let us know if the problem has been resolved on your end, or if you still have trouble. Thank you for your patience as we worked on it.