I think the Clay managed access token doesn’t get set correctly in some waterfalls atm
I don't have specific information about issues with Clay managed access tokens in waterfalls. Waterfalls in Clay are designed to run multiple actions sequentially across different data providers to maximize coverage and minimize costs. They typically involve steps like selecting enrichment types, configuring providers, and setting input columns. To better assist you with this issue, could you provide more details about the specific waterfalls where you're noticing the problem, and any error messages or unexpected behaviors you're encountering?
auth token is off in other places as well
Hey Andreas, Thank you for pointing this out. Checking into your table, it looks like it was fixed right? Typically, to fix this error, you would just need to reselect the token and hit save and run. Thank you for pointing this out and sorry for this.
Thx bo - somehow it worked after a few tries with the individual enrichment, but for the waterfall it’s still there and I can’t fix it
I mean, I just deleted the ones where the auth is missing but when you create a new one - no luck
I tried this on my end and I'm not seeing the same issue as you. Could you record a video showing what's happening so we can better understand how to reproduce it?
You can check my test here: https://cln.sh/lx9PTmcl
Let me know if you need anything else!
ah, nice ok workaround accepted! But the default waterfall doesn’t work, see loom
Hey Andreas, Sorry for the confusion. This error isn't about the Auth - it's that fields are missing inside the waterfall. You're trying to add enrichments but those enrichments are missing their inputs. Simply adding the required inputs would fix it. See here: https://cln.sh/jm0gtFJD
ugh, ok. Sorry for taking the bandwidth. There was an auth thing before and I didn’t look further then when I saw the alert. This all makes sense thx