What’s happening here? The waterfall to find emails worked fine, it has results in basically every row. But for some reason it just won’t show them to me. See the video. I don’t want to edit the configuration because I suspect it’s going to want to run the whole thing again and burn all my credits. The data is sitting there but I can’t output it.
The final validated emails appear in the last column of your table, but validation columns are hidden by default to keep your table tidy. To see your email results, open the Columns Panel and unhide the validation columns - this will show you the emails without needing to edit the waterfall configuration or rerun anything. The data is there, just not displayed by default.
But that’s not what’s happening. As you can see the first one, which I ran as a test, is showing in the main column. The other ones are not. It’s clearly a bug I’m a developer and I am highly fluent with clay and this workflow. I’m trying to figure out where I can get the data without running credits again.
Hi Nick, thanks for reaching out. It could be that the waterfall stopped midway through (later columns in the waterfall never ran), and so the emails never reached the output column. To fix this, I would re-run the waterfall. You won't be charged extra credits if the email was already found upfront, but re-running will help return the final email output. Let me know if you have further questions or need additional help! 😊

This answer is factually incorrect. If I re-run the waterfall it will start the whole thing over again as if it never happened. The Apollo account is connected via my Apollo API key, and you’re going to delete the Apollo data you already got, and then go fetch it again, and I’m going to get charged by Apollo again. This will happen because your software is defective, that’s a design/execution flaw. The reason I am reaching out is because I am trying to get you to help/fix this problem that I have identified. In case you’re not convinced, here’s a video that will clearly demonstrate that what you’re saying isn’t true.
Even better, when I do re-run the waterfall, it doesn’t even fix the problem. It just comes back to the same issue, which is that you’re not displaying the email address. So if I took your advice I’d burn a ton of credits and be back where I started. Can someone on your team look at what’s actually happening here and try to help?
Hi Nick, thanks for your patience here. Sorry that's my bad! One solution is to pull out results from Apollo - when you hover over the Email result, like you did in the video, "Add column" on the left pops up. I've gone ahead and done this for you in a column called "Clay Support Email" - this is a free action. Happy to reissue you credits for your trouble as well.
But this doesn’t fix the problem of showing me the actual email I want from any source. It’s a waterfall, it needs to take the email from one of dozen or so sources and put it in the final column. Also I ran it again on some cells and it didn’t work the second time, so running it again doesn’t help me either. The only choice I seem to have is to build another column from scratch and hope the software works as its supposed to this time. Is having the software work as designed now not one of the choices I have?
Here’s an example:
None of the apollo emails were validated by Zerobounce, so they’re not known to be valid.
When they didn’t exist and another one was found the tool just stopped, but never gave back the output:
I ended up just doing another enrichment can you at least issue the credits for that
It looks like a couple thousand credits at a glance
Hello Nick! Thanks for reaching out! Looks like it was indeed a bug with Zerobounce. Since you already re ran the waterfall I have refunded the 1.65k credits you spent in it. I am also adding additional credits and have refunded a total of 3k for you to continue working on Clay. If you do face this again do reach out and we can file a bug right away. This is a hard to reproduce issue and hence tough to file a bug for unless we already have the situation. Thanks for flagging this and we will keep an eye out incase we see a situation like this again!
OK thank you
I will go ahead and close this out then. Thanks and reach out again if there is anything else!
