facing a new error in "write to other table" - last week it was working fine, no problems at all. But now, when processing new ones, it is giving error you can not write to table because the sequence of write to table integrations is misconfigured. same goes for other tables as well. table link - https://app.clay.com/workspaces/236286/workbooks/wb_2Td26Mt2Tb3X/tables/t_7jGRT8kNpoDi/views/gv_9Yv9qi2P2WZC require fix urgently
Hi Fahad, thanks for reaching out. The issue you're experiencing is due to the lookup column you've set up to the right of the "write to other table" integration. This creates an infinite loop where records are written by the integration and then looked up again, causing the configuration error. Deleting the lookup column should resolve the issue. Let me know if you need further assistance!
Hi Bruno, deleted the loop and its columns, but still giving the same error.
I even deleted the "write to other table" column, and started as fresh enrichment. Error is the same.
Hey there Fahad thanks for reaching out, jumping for Tomas here, was taking a look at this sequence and noticed that in "Jobs Without Recruiter" and "Jobs with Recruiter" tables that you writing to a table that is part of a different workbook called "Final Jobs Tables" in the Mub workbook. What is the goal here for this particular write to table as it is the only one that write to a completely different workbook https://downloads.intercomcdn.com/i/o/w28k1kwz/1240955900/1c9800661a046d2cacc1b7ad6547/image.png?expires=1730837700&signature=3a3b904df46590d5c1a147a0ffc8bf170abc15c29a51c3f0f486e2d9a8b4075d&req=dSIjFsB7mIhfWfMW1HO4zUnfZbnp1hgnYGyBJeQKHwrJYxDBralSeQlgQTHo%0Aei51%0A
some of our team members want to do their work outside of the workbook, example
collecting jobs from with/without recruiter for all team members together
passing them to final table
and then from there each team member have different work structure or preference like someone needs to verify first, someone needs to find phone numbers first.
This can be done within the same workbook, but considering the team there will be so many tabs for each member, around 30+ tables which takes a lot of scrolling and confusion. So probably we will be keeping all the remaining work outside of this workbook.
I checked on what you pointed out, removed that column "write to Mub", still it gave the same error "sequence of write to table integrations is misconfigured" in Jobs with/without recruiter. Then I deleted the "write to" columns from those tables and it worked. Now the table is fine. But, this kept me thinking, if something is being transferred outside of the workbook, and the workbook starts giving these errors, what is the use of it then and why even the option is available to transfer out of workbook. And if this feature is not viable, is there any other alternate "automated way" of transferring out of workbook.
Hey Fahad, thanks for sharing this additional context. Since multiple team members have different table structures they are looking to build it definitely makes sense to send data to other tables outside of this workbook. Write to other table is the best approach here to do so. I'm not aware what the specific setup of the write to table columns were that you deleted, but here are some general tips to avoid the "sequence of write to table integrations is misconfigured" error This error means that one of your write to table columns was set up to create an infinite loop of back and forth data transfer. Write to table is built to send data linearly in one direction. This means instead of correctly sending data from Table A sending data to Table B, and then Table B sending data to Table C, you have created an infinite loop by sending data from Table A to Table B, from Table B to C and from Table C back to Table A or B. If there’s a missing or deleted table in the sequence, this stops the entire process. For next time, to fix this: • Check if any table in the sequence was deleted. • Re-create the missing table, or set up a new sequence to ensure everything is connected properly. Great work using these really advanced features in Clay, keep it up!
Hey Tanvi, thank you for the detailed clarification. I understand and as you know I have updated the columns by deleting the loop. I also deleted "write to columns" from both the jobs table with/without recruiter. I've then created "write to final jobs" columns in both tables. The one created in Jobs WOR is working fine, but that created in with recruiter (Jobs WR) it is still giving same error and I can't understand why this one is still giving error even after deleting the loop and creating a fresh linear write to column. I'd appreciate if you can try this by creating write to "Final jobs - In" with "Jobs WR" and see what's going wrong. Our trial expired a few hours ago and we'll be going for subscription in 2 to 3 days. So I can not check myself. Thanks
here's the link : https://app.clay.com/workspaces/236286/workbooks/wb_2Td26Mt2Tb3X/tables/t_EKUUeQGNEr4M/views/gv_EnBNXJonG2ht You can select any one or two fields for testing
Hey Fahad, thanks for reaching out! I checked your table setup, and it seems like you have more than 10 “write to” actions across your tables. Our system has a limit of 10, so having more than that is causing the error you’re seeing. To get this working smoothly, I recommend reducing the “write to” actions to fewer than 10. This should prevent the error from appearing again. Let me know if there’s anything more I can help with or if you need further assistance making these adjustments!
Hey Bo, I've moved some of the tables outside of the workbook to reduce the "write to columns". I still can't create "write to" because of ended trial. Once we subscribe, I'll test it out.
Hello Fahad! I unlocked the write to table feature for another week so you can test it out.
Thank you so much Tomi
it's still asking to upgrade
Hm, my fault. Can you try again and let me know if it works? I added it on this workspace, let me know if it is the incorrect one.
the feature got unlocked, but write to table is still giving the same error
Hi Fahad, the “Write to Table” error is always due to one of two things: 1. Linked Table Limit: Clay supports linking up to 10 tables. If there are more than 10 tables linked together, this can cause errors. 2. Deleted Table or Value: If a table or specific values were deleted, this can disrupt the connections and lead to errors. To resolve this, please double-check: • That all “Write to Table” actions are pointing to the correct table. • That there are no more than 10 tables linked. I do currently see 10 tables still Additionally, I noticed a few entries in the table you sent that might need updating. Could you try removing those and re-running the setup? Let me know if this helps or if you need further assistance!
Hi Bo, thanks for getting back to me with the new info. point no. 1:
If the default limit if of 10 tables, how come it allowed us to create and link more than 10 tables?
When we created those tables for the first time and linked, everything worked fine. But after the next run of jobs, it started giving errors/issues, first there was loop issue, then there was "write to table limit 10" and now the tables should only be 10.
Anyways, if the table limit is 10, is that limit set to single workspace or overall linking to tables even outside the workspace? Because atm we have 4 workspaces, but each workspace contains less than 10 tables and all are linked.
\ point no. 2:
Yes tables and values were deleted, due to write to limit and loop issues
following your advice, today first I deleted all the data from the tables, the issue was still there. then I deleted the links from the table, deleted some tables and started one by one (creating similar new tables) and linking them to the remaining tables back. before linking to old tables, there was no error, after linking, same error appeared.
A. That all “Write to Table” actions are pointing to the correct table - All are correctly linked B. I'm actually waiting for your response/final support. In the meantime, we have started creating new tables and removing the all tables completely to see if the error is because of data/values. For limit to 10 tables, need to create a different workflow/strategy - because the current one is unavoidable
Update: Step by Step work
Cleared all data/values - not worked
Limit our tables to 10 - not worked
Limit our write to other tables to 10 - worked
What I understand from this, we only have to work in 10 tables and with 10 write to limits. Our workflow can not be limited to "10" either tables or write to's. Is there any option or feature Clay team can increase the limit to a min 25 each. If not, what is the alternative or workaround for this?
Correct, the maximum number of downstream write-to-table operations is 10. We have to limit the number of nodes because a write to one table could trigger many other columns/integrations in the receiving table, which could write to other tables with their own integrations and writes, etc.. The intent is to avoid a cascade of events that would hurt performance. One option to consider would be to use HTTP API integrations as the output for a given origin table, and create webhooks Correct, the maximum number of downstream write-to-table operations is 10. We have to limit the number of nodes because a write to one table could trigger many other columns/integrations in the receiving table, which could write to other tables with their own integrations and writes, etc.. The intent is to avoid a cascade of events that would hurt performance. One option to consider would be to use HTTP API integrations as the output for a given table, and create webhooks to use as inputs for the receiving/destination tables.
.png){kind=logo}
