Trouble with Email Waterfall: Auto-Update, Running Order, and Credit Usage

Hey Clay geniuses! So I started an Email Waterfall and unchecked "auto-update" and then clicked "save". I thought this meant it wouldn't run until I clicked "run" myself. But when I checked a few minutes later, I saw that all the waterfall providers were automatically running EXCEPT the first one 🤔

1.
Any idea what happened here and how I can prevent that in the future?
2.
Since the first provider (Prospeo) got skipped...can I run it now, or will it trigger the waterfall all over again with all the other providers?
3.
Does Clay use credits only when an email is found, or does it use a credit just for an attempt?

Thank you so much, y'all are a godsend!

6 comments

Jaemin Y.
·
·
https://app.clay.com/workspaces/122070/tables/t_Nj8gQtszXZ47/views/gv_7mWq7bVBVNW7
Clay Team
APP
·
·
Ah yes I can see what happened here.1. It seems that you turned off the auto-update, but only for the prospeo column. That's why it did not run, but the other ones did run. 2. You can run it now, but it will re-trigger the columns after it. I would recommend that you filter your table for the ones that do not have an email address, and then run the prospeo column only for those rows. 3. This is different for all our enrichments, but in the case of the email waterfall, you are only charged if it finds an email.Hope that helps :)
Jaemin Y.
·
·
Great! How do you turn off the "auto update" for the other columns when you set up the email waterfall? When I set it up, there's just one "auto update" toggle. And I untoggled it. But it seems like that only toggles for the first provider?
Jaemin Y.
·
·
Also, I'm running the Prospeo column now...but most of the ones I try keep saying "error". Any idea what might be going on here?
Clay Team
APP
·
·
Hey! jumping in here, Jaemin Y.... The table-wide auto-update button is in the ellipses next to the table's name
df9956fd-f250-4bce-b741-57cddacc61da.png(35 kB)
Clay Team
APP
·
·
Could you share the link to your table where Prospeo is erroring out, is it a "Bad request" error message? If so, based on previous engineering responses... tl;dr Prospeo is unable to check the MX records for some of those domains so it just errors out. That's something specific they have in place and mentioned in their site https://prospeo.io/api/email-finder#::~~::text=The%20domain%20name%20you%20submitted%20is%20not%20reachable%20or%20does%20not%20have%20valid%20MX%20records

Trouble with Email Waterfall: Auto-Update, Running Order, and Credit Usage | Clay