Troubleshooting Infinite Loop Error in Full Enrichment Prospecting Setup | Clay

Troubleshooting Infinite Loop Error in Full Enrichment Prospecting Setup

Hi team, I am unable to add additional providers to my "find work email" waterfall (Link to table - name "Full Enrichment Prospecting".) Each time I attempt to add a provider, it gives me an error that it would cause an infinite loop. The waterfall output column is Recipient Email. Thanks!

12 comments

Channeled
APP
·
·
Based on the information available, the infinite loop error typically occurs when there's an issue with the waterfall configuration. To properly set up an email waterfall: 1. Make sure you have the required "corner pieces" data in your table: • Full name • LinkedIn profile URL • Company domain • Company LinkedIn URL 2. When adding providers to your waterfall: • Click "Add Column > Add Enrichment" • Search for "Waterfall" • Select your data type • Use "Add Action" to include additional providers • Ensure proper ordering of your integrationsIf you're still experiencing the infinite loop error after following these steps, you'll need to request human support to investigate the specific configuration of your "Full Enrichment Prospecting" waterfall. Sources: Enrich People (Waterfalls) [CRM Enrichment] - Clay University Building a data waterfall | Documentation | Clay University Custom Waterfall
Channeled
APP
·
·
Looks like you're still looking for help. We're escalating this over to our support team and someone should be in touch soon. In the meantime, feel free to include any other information that may be helpful in solving your issue!
Dustin S.
·
·
I do have the corner pieces of data, however, I am pulling in user linkedin URL from a separate waterfall - wondering if this could be the issue?
LuisArturo
·
·
Hey there Dustin thanks for reaching out, let me take a look at this, question which provider are you seeing this issue occur with or does it happen when you try to add any provider?
Dustin S.
·
·
Thank you! It is whenever I try to add any provider.
LuisArturo
·
·
Hey there Dustin took a look at this, I believe the issue is here is what you mentioned earlier that the LinkedIn URL is being pulled from your other waterfall and because that waterfall takes in the result of this one, it is causing the loop. The interesting thing here is even after configuring the email waterfall to not use the results from this second one, it still causes the issue. In this case what you can do is you a standalone email integration and use a conditional formula to prompt it to not run if the "Recipient Email" column has a value.
Channeled
APP
·
·
Hi Dustin S.! This thread was recently closed by our Support team. If you have a moment, please share your feedback:
Channeled
APP
·
·
Thanks! We've reopened this thread. You can continue to add more detail directly in this thread.
Dustin S.
·
·
Hi there, so is it a bug? Is there no way around except doing standalone email integrations? Also, when I set up the standalone ones with that run condition, is there a way to get it to wait until the waterfall is complete to see if that column has a value? Thanks
Bo (.
·
·
Yes, it's a bug that's been escalated to engineering. For now, you can: 1. Set up standalone email integrations with conditional formulas 2. Make them wait for previous providers by adding conditions that check if earlier provider email fields are empty before running Example formula: Only run if /provider1_email and /provider2_email are empty [App: Article Inserter]
Bo (.
·
·
Good news! Happy to report that we heard back from the team and this issue should be fixed. Thank you for your patience as we worked on it. Please let us know if the problem has been resolved on your end, or if you still have trouble.
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.