Troubleshooting Connected Tables Errors in Cross Table Waterfall Enrichment | Clay

Troubleshooting Connected Tables Errors in Cross Table Waterfall Enrichment

Hi guys, we have some connected tables through "write to other table". This is happening 5 times like in a cross table waterfall enrichment. I duplicated all of them one after the other to a different folder because we wanted to test something. Then I wanted to connect them to the duplicated ones, because the connection still was up for the initial table. With the first table it worked, but for the 2nd, 3rd, 4th and 5th table, I got an error. The error happens everytime I try to enter the "edit column" Option:

13 comments

Channeled
APP
·
·
👋 Hey there! Our support team has got your message - we'll be back in touch within 24 hours (often sooner!). If you haven't already, please include the URL of your table in this thread so that we can help you as quickly as possible!
Hendrik H.
·
·
https://app.clay.com/workspaces/307417/tables/t_eQ64YzUhm6zb/views/gv_D6tPRpBUDK86
Bo (.
·
·
Hey, thanks for reaching out! Could you please send us the table where this issue is happening? It’s important to note that you can’t link more than 5 tables together, as it can cause too much data consumption. You need to reduce the number of connections or simplify the setup. Sorry for the inconvenience! Let me know if you need help adjusting it. 😊
Hendrik H.
·
·
I did, just check my last reply
Hendrik H.
·
·
Thanks for jumping on it 🙂
Hendrik H.
·
·
Does the limitation affect Tables as well that are "connected" through http request and webhook?
Hendrik H.
·
·
So this is happening to the table structure: Table1: https://app.clay.com/workspaces/307417/tables/t_AUUWf4UbM955/views/gv_VtfTbf9naMSW (This is the only table where it works) Table2: https://app.clay.com/workspaces/307417/tables/t_eQ64YzUhm6zb/views/gv_D6tPRpBUDK86 Table3: https://app.clay.com/workspaces/307417/tables/t_6AmXVwpJ6u73/views/gv_XWScjdYTTYPX Table4: https://app.clay.com/workspaces/307417/tables/t_xnP792pc3cUb/views/gv_tUB92gTgMxSd Table5: https://app.clay.com/workspaces/307417/tables/t_6kuzsHNgNyJd/views/gv_qDzwiAT854J7 (From here, we push it back into our system, so no "write to other table" here)
Hendrik H.
·
·
Those are a copy of the initial structure that we have in another folder. We wanted to make a copy as a staging/testing environment. They are still connected to the initial tables. Therefore I now need to connect the tables to the copies.
Hendrik H.
·
·
Is there a way to get more bandwidth with an enterprise account? We are already on the highest tier and our token consumption will become quite high, once we cover our processes with clay.
Hendrik H.
·
·
We are seeing alot of errors the last weeks, so if we get more stability through the enterprise plan, we are more than willing to take that route.
Daniel K.
·
·
Hi Hendrik! Thank you for your patience with this issue. It appears that this issue may arise when the write to table is deleted or when multiple tables (more than 5-6) are connected. I have escalated this to our team as several users have reported experiencing this issue. Our engineering team is actively working on resolving this as we speak. I will keep you updated as soon as I have any new information about this bug. If you don't hear from me, rest assured that the engineering team is still on it. Once there's progress, this conversation will automatically reopen on my end, and I'll follow up with you. In the meantime, as a temporary workaround, you can create a new "write to other" column and proceed as usual. Regarding enterprise solutions, our Enterprise partners indeed have additional benefits and capabilities, including passthrough tables. It might be beneficial to have a conversation with them. Here's the link for more information: https://clayhq.typeform.com/clay-plus?typeform-source=www.clay.com Sorry for any inconvenience caused!
Channeled
APP
·
·
Hi Hendrik H.! This thread was recently closed by our Support team. If you have a moment, please share your feedback:
Bo (.
·
·
Hello there! Happy to report that we heard back from the team and this issue should be fixed. Thank you for your patience, feel free to try again and let us know if the problem has been resolved on your end.