Employee Headcount Waterfall Issue: Second Step Not Aggregating

Garrett W. · 2025-11-18T04:36:01.958Z

find employee headcount waterfall not aggregating second step into the waterfall https://app.clay.com/workspaces/532984/tables/t_0t4709cZpDQZTqu354d/views/gv_0t31ys7kzWZqKpkUDmg

Employee Headcount Waterfall Issue: Second Step Not Aggregating | Clay

13 comments

· Sorted by Oldest

Clay Support
APP
·
·
The waterfall isn't aggregating because the first step is failing with "No Role Found" errors. In waterfalls, the process works sequentially - if the first column successfully retrieves data, subsequent steps are skipped to preserve resources.
Since your first step is failing, the waterfall continues to the second step which finds employees, but the final result column shows zeros because the waterfall logic requires the sequence to work properly. [1]
Check your run conditions in the first column and ensure the input data (like company domain) is properly formatted. You can click the "explain" button on the failed rows to see why the run condition wasn't met.
Clay Support
APP
·
·
Is that what you were looking for?
Garrett W.
·
·
yes so i would think the second value would be returned in the waterfall
Clay Support
APP
·
·
If you still need help resolving the issue with your employee headcount waterfall, I’m here to assist. Would you like to provide more details about what you’re trying to achieve or any specific challenges you’re facing?
Clay Support
APP
·
·
You're right to expect that! The waterfall should return the second step's value when the first fails. However, waterfalls only continue to the next provider when the previous one doesn't find the specific data point you're looking for. [1]
In your case, even though the second step finds employees, the waterfall logic requires the sequence to work properly for the final result column to populate. The "Run condition not met" messages suggest there might be validation issues preventing the data from flowing through to your final column.
Check if your run conditions are properly configured for the data to pass from the second step to your final result column.
Clay Support
APP
·
·
Did that answer your question?
Clay Support
APP
·
·
If you still need additional help with your employee headcount waterfall issue, I’m here to support you. Would you like to share more about what you’re trying to resolve or any specific difficulties you’re encountering?
Garrett W.
·
·
lol w0t human pls
Clay Support
APP
·
·
I understand you’d like to speak with a human agent. I’m routing you to our team now so they can assist you further.
Clay Support
APP
·
·
Our support team has got your message and we'll get back to you soon! We're currently outside of our standard office hours (9 AM to 9 PM EST, Monday through Friday), so it may take a little longer for us to respond.
If you’re dealing with a specific table, drop the URL below so we can help you quicker. Otherwise, someone from our team will be in touch soon!
image.png(93 kB)
Mayato (.
·
·
Hi Garrett, thank you for reaching out and for your feedback. You’re right this seems odd. The People Data Labs output for employeeCountByCriteria should be a number like the following:
Could you let me know where you found this waterfall action? I’d love to take a closer look and share feedback to the team.
Loading attachments
Mayato (.
·
·
FYI, I have tried to run "Get Employee Count by Criteria" waterfall enrichment in Clay and it placed the employee number data correctly in the field. https://www.loom.com/share/f42a33b1e813419589a92158e983d36f
Clay Support
APP
·
·
We haven't heard back from you here, so we're going to go ahead and close this thread out.
Still need help here? Reply back and someone will jump back in.
Have a question thats not related to this thread? We recommend kicking off a new ticket in the support channel!

Clay Support
APP
·
·
The waterfall isn't aggregating because the first step is failing with "No Role Found" errors. In waterfalls, the process works sequentially - if the first column successfully retrieves data, subsequent steps are skipped to preserve resources.
Since your first step is failing, the waterfall continues to the second step which finds employees, but the final result column shows zeros because the waterfall logic requires the sequence to work properly. [1]
Check your run conditions in the first column and ensure the input data (like company domain) is properly formatted. You can click the "explain" button on the failed rows to see why the run condition wasn't met.
Clay Support
APP
·
·
Is that what you were looking for?
Garrett W.
·
·
yes so i would think the second value would be returned in the waterfall
Clay Support
APP
·
·
If you still need help resolving the issue with your employee headcount waterfall, I’m here to assist. Would you like to provide more details about what you’re trying to achieve or any specific challenges you’re facing?
Clay Support
APP
·
·
You're right to expect that! The waterfall should return the second step's value when the first fails. However, waterfalls only continue to the next provider when the previous one doesn't find the specific data point you're looking for. [1]
In your case, even though the second step finds employees, the waterfall logic requires the sequence to work properly for the final result column to populate. The "Run condition not met" messages suggest there might be validation issues preventing the data from flowing through to your final column.
Check if your run conditions are properly configured for the data to pass from the second step to your final result column.
Clay Support
APP
·
·
Did that answer your question?
Clay Support
APP
·
·
If you still need additional help with your employee headcount waterfall issue, I’m here to support you. Would you like to share more about what you’re trying to resolve or any specific difficulties you’re encountering?
Garrett W.
·
·
lol w0t human pls
Clay Support
APP
·
·
I understand you’d like to speak with a human agent. I’m routing you to our team now so they can assist you further.
Clay Support
APP
·
·
Our support team has got your message and we'll get back to you soon! We're currently outside of our standard office hours (9 AM to 9 PM EST, Monday through Friday), so it may take a little longer for us to respond.
If you’re dealing with a specific table, drop the URL below so we can help you quicker. Otherwise, someone from our team will be in touch soon!
image.png(93 kB)
Mayato (.
·
·
Hi Garrett, thank you for reaching out and for your feedback. You’re right this seems odd. The People Data Labs output for employeeCountByCriteria should be a number like the following:
Could you let me know where you found this waterfall action? I’d love to take a closer look and share feedback to the team.
Loading attachments
Mayato (.
·
·
FYI, I have tried to run "Get Employee Count by Criteria" waterfall enrichment in Clay and it placed the employee number data correctly in the field. https://www.loom.com/share/f42a33b1e813419589a92158e983d36f
Clay Support
APP
·
·
We haven't heard back from you here, so we're going to go ahead and close this thread out.
Still need help here? Reply back and someone will jump back in.
Have a question thats not related to this thread? We recommend kicking off a new ticket in the support channel!