Struggles of Setting Up a Waterfall: Key Challenges and Frustrations | Clay

Struggles of Setting Up a Waterfall: Key Challenges and Frustrations

Going to be honest -- setting up a waterfall is absolutely brutal. Insane amount of bugs. Have had to restart 9-10 times and still can't get it to work properly.

4 comments

Owen C.
·
·
Hey Mathew, thanks for reaching out! Thanks for this! We're always looking to make the product better and this feedback is super helpful for us. We're going to pass this over to our product team so they can better evaluate things and see if/where this might fit into the roadmap as a future improvement.
Mathew I.
·
·
RocketReach waterfall exit formula in the default mobile phone waterfall is broken.
Doesn't let you change connection accounts of a particular step in the waterfall (gives "infinite loop error")
Renaming columns in the waterfall config does not reflect changes when saved.
Input variables to individuals steps typically default to incorrect values (usually to other values in the waterfall, which should not be the case) and automatically change back to the wrong values even when I manually change them.
Can't create my own formulas for waterfall exit values. Very often these enrichments return arrays and I want control over which value gets returned.
Absolutely needs to be a way to measure "waterfall status" ("Ran and succeeded", "Ran and failed", "did not run").
Probably should be able to access a cells "run status" in formulas which would solve this
Owen C.
·
·
Thanks for these points Mathew, would love to learn a bit more about your experience here: * What aspect of the exit formula with RocketReach is broken? * Yes, there's a lot of logic built in to ensure these waterfalls work properly which makes adjusting them after creation tricky - working on a fix here :) * Good point, as of right now this is related to previous statement. * Yes! This was a bug we ran into that should've been resolved, if not could you share the URL to the Clay table where this occurred so we can take a closer look? * Solid points of feedback! Will share this with our team. :) Waterfalls are one of the most complex parts of Clay as there is a lot of logic built on the backend to prevent unnecessary credit spend. Plus, many variables such as what inputs you use and how many data providers are included alters this logic. Seriously, we appreciate you taking the time to share these insights! 🙌 I’ve passed this feedback along to our team to explore how we can make improvements. Thank you for helping us make Clay even better! :)
Channeled
APP
·
·
Hi Mathew I.! This thread was recently closed by our Support team. If you have a moment, please share your feedback: