Hey guys, email validation in waterfalls doesn't work with the "safe to send" option toggled. When I select to exclude catch-all email from one email with a separate enrichment, it will soundly mark catch-all as invalid When I select the same exact option in the waterfall (using ZeroBounce in both cases), it will find the exact same email address and select it as valid even though it's a catch-all. Loom
š¤ You've caught us outside of our support hours (9am-9pm EST), but don't worry - we'll be back in touch within 24 hours (often sooner!). If you haven't already, please include the URL of your table in the thread below so that we can help you as quickly as possible!
Hey Leon, As always, thank you for the clear videoāitās super helpful! Quick question: Is it possible that the āsafe to sendā was added after everything had already run, and the columns werenāt triggered to re-run? Iām asking because when I tried to re-run it (at first, I got the API key credits empty error), but now itās showing as invalid. This made me think that might be the case here. Hereās a GIF showing exactly what I mean. š https://downloads.intercomcdn.com/i/o/1174211835/b27c08c215644a954e9a4a47/CleanShot+2024-09-09+at+_10GEPDnHeC.gif?expires=1725908400&signature=a71daa89c24a0814370a5c15798d5db44df9ceee86b4e8c4c572669a2ec359a2&req=dSEgEst%2FnIlcXPMW1HO4zZ9A%2Fe4W506rmiPcHPJI8UmUCFEI4tsnDh%2BNWPvD%0AwZsn%0A
This thread was picked up by our in-app web widget and will no longer sync to Slack. If you are the original poster, you can continue this conversation by logging into https://app.clay.com and clicking "Support" in the sidebar. If you're not the original poster and require help from support, please post in 02 Support.