Enrichment Error Drains Findymail Credits: Seeking Solutions

Lazar Radivojevic · 2025-06-20 06:54:51.550002+00

Hey team, I was running an enrichment on a filtered view, but for some reason the enrichment ran on a non filtered view as well and completely drained my Findymail credits (using own account through API) I've never had this problem before, and I only realized when I got a notification from Findymail that I used all of my credits. I've done it this way hundreds of times before, with no issue

Enrichment Error Drains Findymail Credits: Seeking Solutions | Clay

10 comments

· Sorted by Oldest

Channeled
APP
·
·
Filtered views should only enrich the rows you're viewing, not the entire table. This unexpected behavior suggests something went wrong with your filter setup or enrichment configuration. To prevent this in the future, you can use conditional runs as an additional safeguard: 1. Go to Run Settings of your enrichment column 2. Add a conditional formula in the "Only run if" box to specify when enrichment should run Since this behavior is unusual and you've used filtered views successfully before, if you need further help investigating what caused this specific issue, you should request human assistance by clicking on "Talk to a person."
Sources: Guide: Ways to save Clay credits | Documentation | Clay University Guide: Ways to save Clay credits | Documentation | Clay University
Bo (Clay)
·
·
Hey, sorry about that—what likely happened is that the enrichment column was tied to a dependency at the full table level, not just the filtered view. If that dependency changed (like a column it relies on got updated), it would have triggered a rerun for all rows, not just the filtered ones. Let me know if you want help checking which dependency caused it.
Lazar Radivojevic
·
·
Hey Bo, there shouldn't have been any dependency on the full view, because it was a template that I imported that ran wrong (also another thing I'd like to have checked out if possible)
LuisArturo (Clay)
·
·
Hey there Lazar thanks for reaching out, do you mind sending the link (url) to the table so we can take a look?
(52 kB)
Lazar Radivojevic
·
·
https://app.clay.com/workspaces/362785/workbooks/wb_0sy3wcgCEQAR8XbWBqW/tables/t_0sy3wcgdCx27dga6f2R/views/gv_0sychzaTJGktkECUA6y
LuisArturo (Clay)
·
·
Thanks taking a look at this also, to confirm was the template used here your own template?
Lazar Radivojevic
·
·
It was indeed
Lazar Radivojevic
·
·
Lucky's Waterfall
LuisArturo (Clay)
·
·
Hey there sorry for the delay here, quick question where, both filters already in place here when the template was added. Additionally taking a look at this what most likely happened here was since the formula for the Validate email refreshed it self as it was looking for the column that makes its requirement and this refresh occurs for the entire table even for rows that are not visible and which integrations take as a que to run. Regardless what we can do here is refund you Clay credits in the value of API credits that were used up here
(53 kB)
Channeled
APP
·
·
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.

Channeled
APP
·
·
Filtered views should only enrich the rows you're viewing, not the entire table. This unexpected behavior suggests something went wrong with your filter setup or enrichment configuration. To prevent this in the future, you can use conditional runs as an additional safeguard: 1. Go to Run Settings of your enrichment column 2. Add a conditional formula in the "Only run if" box to specify when enrichment should run Since this behavior is unusual and you've used filtered views successfully before, if you need further help investigating what caused this specific issue, you should request human assistance by clicking on "Talk to a person."
Sources: Guide: Ways to save Clay credits | Documentation | Clay University Guide: Ways to save Clay credits | Documentation | Clay University
Bo (Clay)
·
·
Hey, sorry about that—what likely happened is that the enrichment column was tied to a dependency at the full table level, not just the filtered view. If that dependency changed (like a column it relies on got updated), it would have triggered a rerun for all rows, not just the filtered ones. Let me know if you want help checking which dependency caused it.
Lazar Radivojevic
·
·
Hey Bo, there shouldn't have been any dependency on the full view, because it was a template that I imported that ran wrong (also another thing I'd like to have checked out if possible)
LuisArturo (Clay)
·
·
Hey there Lazar thanks for reaching out, do you mind sending the link (url) to the table so we can take a look?
(52 kB)
Lazar Radivojevic
·
·
https://app.clay.com/workspaces/362785/workbooks/wb_0sy3wcgCEQAR8XbWBqW/tables/t_0sy3wcgdCx27dga6f2R/views/gv_0sychzaTJGktkECUA6y
LuisArturo (Clay)
·
·
Thanks taking a look at this also, to confirm was the template used here your own template?
Lazar Radivojevic
·
·
It was indeed
Lazar Radivojevic
·
·
Lucky's Waterfall
LuisArturo (Clay)
·
·
Hey there sorry for the delay here, quick question where, both filters already in place here when the template was added. Additionally taking a look at this what most likely happened here was since the formula for the Validate email refreshed it self as it was looking for the column that makes its requirement and this refresh occurs for the entire table even for rows that are not visible and which integrations take as a que to run. Regardless what we can do here is refund you Clay credits in the value of API credits that were used up here
(53 kB)
Channeled
APP
·
·
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.