We seem to have a bug where write to other table is erroring out and cant run, with no obvious reason why: https://app.clay.com/workspaces/12893/workbooks/wb_0swaqncmpbQbVr3VB9z/tables/t_0swaqo0AcSDAAawmvFg/views/gv_N8AvpdNQsmUs
There could be a few reasons why you're encountering an error when using the write to table feature in Clay. Here are some common issues and solutions: 1. Invalid credentials: Ensure your Clay API key is correct and properly connected. Check under Settings > Connections > Clay. 2. Misconfiguration: The error might occur if you're writing to a deleted column or sending data to a table that references another table. Reconfigure your write to table integrations and double-check that all columns and tables exist and are correctly set up. 3. Processing issues: If a specific column isn't processing correctly, try these steps: • Delete the affected column • Create a fresh column • Re-map your data to the write to table (ensure auto-dedup is activated in the other table) If these solutions don't resolve your issue, you may need to request human assistance for further troubleshooting.
https://app.clay.com/workspaces/12893/workbooks/wb_0swcery3TTSdWVnEMnM/tables/t_0swces5DkpCHaoRRoWW/views/gv_TVHQk6ag6bRr this table also having same issues
The data has run on the first table partially, but is still erroring on the second, it seems like there could be throttling issues?
spoke too soon, this isn't running
Hey there J thanks for reaching out, sorry for the delay. I've escalated this to our engineering team to help look into it. We'll follow up here as soon as we know more!
Thanks LuisArturo seems Claygent also playing up : https://app.clay.com/workspaces/12893/workbooks/wb_0swi2wlopkinNyDMb9V/tables/t_0swi2xdsovgNomevmfq/views/gv_0swi2xdQZMbymfw7VRp
Hey there heard from the team that the Write to table issue should be fixed now.
LuisArturo this is not resolved. I uploaded this data this morning and there are still issues with "Write to table" https://app.clay.com/workspaces/12893/workbooks/wb_0swju4yRuyNA6MmT5ZF/tables/t_0swju5csaSHNepXf7sv/views/gv_JZ5isrUc37QJ https://app.clay.com/workspaces/12893/workbooks/wb_0swjudzw4AD7ZfWkFYu/tables/t_0swjueeJbHXJzJ59fFy/views/gv_JZ5isrUc37QJ https://app.clay.com/workspaces/12893/workbooks/wb_0swjvnyxp6orGxPE6Pn/tables/t_0swjvodP6wt8fXg6niu/views/gv_JZ5isrUc37QJ
Sorry LuisArturo, team still having issues here
Hey there Joel sorry and Teodora sorry about that let me check back in with the teams and see what is happening here.
Hey there sorry for the delay here, can you try this again, a fixed was pushed out here.
LuisArturo https://app.clay.com/workspaces/12893/workbooks/wb_0swylqxNTfcrf3XV2KX/tables/t_0swylrbzjtUr7b7a6TB/views/gv_JZ5isrUc37QJ https://app.clay.com/workspaces/12893/workbooks/wb_0swylvtvGqnkHdaX3ZC/tables/t_0swylw9fTAmJvEjxHoC/views/gv_JZ5isrUc37QJ this is data uploaded today, the Write to table columns still don't run properly
Hi Teodora, I just checked the table links you shared and I don't see a error state for the Write to Table columns. Can you confirm if you are still facing the issue and if so do you mind pointing me to the column name and some of the example rows I can look at. Thank you!
Smit V. I don't know if you had a chance to catch up with the previous messages, but the write to table columns in the email waterfall have issues, some of the rows are not running. Here I have pined the Write to "Ready for Instantly" Table and Write to "Microsoft" I filtered the rows that haven't run on Write to "Ready for Instantly" Table, so that you can have a closer look. Feel free to filter on the other column Same happens with the other table I sent, and the rest of the tables created in the past 2 weeks. You might not be able to notice this issue on all of them because i re-run them https://app.clay.com/workspaces/12893/workbooks/wb_0swylqxNTfcrf3XV2KX/tables/t_0swylrbzjtUr7b7a6TB/views/gv_JZ5isrUc37QJ
Hey there Teodora, taking a look at your table again, I am able to get the rows to run here. Are you still experiencing this in other tables as well?
yes, we are experiencing this with all of the tables LuisArturo
LuisArturo i am not sure if we are looking at the same table https://app.clay.com/workspaces/12893/workbooks/wb_0swylqxNTfcrf3XV2KX/tables/t_0swylrbzjtUr7b7a6TB/views/gv_JZ5isrUc37QJ
Hey Teodora made a loom going over this: https://www.loom.com/share/a8c42449a21a4b409386dc3c84590a1a?sid=b5f273dd-6956-476f-811c-b1535a69e2c2
hey LuisArturo these rows should run automatically once the data is uploaded, same as the others. The issue here is that some of the rows for "write to table" run automatically and some don't. If you want, you can test with a small sample. you can download data from 2.a Import Data table To get the rows we would need to manually run those that haven't run
I see thank you for sharing let me check in with the team Theodora, this may be related to another issue entirely.
Sorry for the long delay here Teodora, checked in with the team and the other issue I believe may have caused this was not the case. Additionally, went ahead and ran a test with the data you mentioned to see what would happen and I was still unable to recreate this issue on my end, could you send a loom here showing what is happening as am unable to get this reoccur and do not want to leave this ticket until we know that it is no longer an issue,
Hey Teodora sorry for the long delay here, thank you for sharing the loom definitely helps see what is going on here, have gone and asked the engineering team to see what is happening as after reviewing the table there is nothing that stands out from a Table setup viewpoint that would keep these write to table from triggering.
LuisArturo The setup shouldn't be an issue. Do you know why all of the rows are not running in the Write to Table columns?
Hey Teodora — thanks for your patience. Can you try re-running the rows that haven’t triggered in the Write to Table column? Let me know how it goes.
Hey Teodora sorry for the delay here, thank you for letting us know checking in with the team again about this.
LuisArturo Bo (. any update here? it has been a month since we opened the thread and no progress on the issue
Hey Teodora—totally hear you, and I know how frustrating this must be, especially across so many workbooks. Right now, the workaround is to re-run the rows manually when Write to Table doesn’t trigger, but we agree that’s not sustainable long term. The team has linked this to an internal issue and it’s now back in the queue for engineering review. They’ve flagged it as needing deeper investigation due to missing logs and lack of run IDs on the stale rows. Do you have any extra tables that we can present them ? That might help to speed things up. We don’t have an ETA yet, but it’s on their radar, and we’ll keep pushing for updates. In the meantime, keep flagging affected tables—we’re here to help minimize the impact as best we can. Let me know if you want me to follow up on anything specific.
.png){kind=logo}
