Issue with Send Table Data: Duplicated Config Causes Errors

Joel Blackburn · 2025-07-14 07:48:48.434798+00

Send Table Data not working, duplicated config from a column that is working on another table (duplicating also previously didn't cause errors -

10 comments

· Sorted by Oldest

Clay
APP
·
·
If your "write to table" function isn't working after duplicating a column configuration, try using the Force Run option in the table settings. If that doesn't resolve it, follow these steps: 1. Delete the affected column 2. Create a fresh column 3. Re-map your data to the destination table Also check that you haven't exceeded the maximum of 10 connected tables (across all workbooks) and ensure data flows in a linear direction (A → B → C) without loops.
Sources: Send table data | Documentation | Clay University Send table data | Documentation | Clay University
Laurent Baillot
·
·
I'm running into the same problem - duplicating this workbook used to work fine, now the duplicate loses the connections between tables: https://app.clay.com/workspaces/195674/workbooks/wb_0szhhhgU9GSV4G3jMPM
Clay
APP
·
·
When you duplicate a table or workbook in Clay, only the header structure is copied - the data and connections aren't transferred automatically. This is by design: duplicating a table will only copy the sources, not all the data within the table. To restore connections between tables after duplication, you'll need to use the "write to table" feature to re-map your data fields to the corresponding columns in your new tables. This will transfer the information and re-establish the connections between your duplicated tables.
Sources: Table management settings | Documentation | Clay University Table management settings | Documentation | Clay University
Laurent Baillot
·
·
https://app.clay.com/workspaces/195674/workbooks/wb_0szhhhgU9GSV4G3jMPM
Clay
APP
·
·
Hi - thanks for reaching out! I see that for the original table that you duplicated, the connection was between 0. Jobs and 1. Branches. When creating a copy now, I see that this link has been transferred over, but the CSV Import that is used as a source has not also been linked over. I am not sure why you weren't seeing the connection between those two tables the first time you duplicated it As a note, when you duplicate a workbook, the source does not get duplicated. You'll have to go in and add it in again. Original Workbook
(217 kB)
Duplicated workbook:
(159 kB)
Let me know if that makes sense
Laurent Baillot
·
·
this is the original notebook. All the links disappear upon duplication
LuisArturo (Clay)
·
·
Hey there J thanks for reaching out, how can we help you?
Laurent Baillot
·
·
hi, the bug is still ongoing. waiting for Smit (Clay) to share a solution from engineering https://clayrunhq.slack.com/archives/C025KSBLPGX/p1752771718771289?thread_ts=1752701103.975539&cid=C025KSBLPGX
Clay
APP
·
·
Hi J, Thanks for reaching out to support. Our engineering team is actively working to fix this issue. We appreciate your patience. -Nicole
Nicole Goot
·
·
Good news! Happy to report that we heard back from the team and this issue should be fixed. Try a quick refresh (Cmd/Ctrl + Shift + R) and let us know if the problem has been resolved on your end, or if you still have trouble. Thank you for your patience as we worked on it.

Clay
APP
·
·
If your "write to table" function isn't working after duplicating a column configuration, try using the Force Run option in the table settings. If that doesn't resolve it, follow these steps: 1. Delete the affected column 2. Create a fresh column 3. Re-map your data to the destination table Also check that you haven't exceeded the maximum of 10 connected tables (across all workbooks) and ensure data flows in a linear direction (A → B → C) without loops.
Sources: Send table data | Documentation | Clay University Send table data | Documentation | Clay University
Laurent Baillot
·
·
I'm running into the same problem - duplicating this workbook used to work fine, now the duplicate loses the connections between tables: https://app.clay.com/workspaces/195674/workbooks/wb_0szhhhgU9GSV4G3jMPM
Clay
APP
·
·
When you duplicate a table or workbook in Clay, only the header structure is copied - the data and connections aren't transferred automatically. This is by design: duplicating a table will only copy the sources, not all the data within the table. To restore connections between tables after duplication, you'll need to use the "write to table" feature to re-map your data fields to the corresponding columns in your new tables. This will transfer the information and re-establish the connections between your duplicated tables.
Sources: Table management settings | Documentation | Clay University Table management settings | Documentation | Clay University
Laurent Baillot
·
·
https://app.clay.com/workspaces/195674/workbooks/wb_0szhhhgU9GSV4G3jMPM
Clay
APP
·
·
Hi - thanks for reaching out! I see that for the original table that you duplicated, the connection was between 0. Jobs and 1. Branches. When creating a copy now, I see that this link has been transferred over, but the CSV Import that is used as a source has not also been linked over. I am not sure why you weren't seeing the connection between those two tables the first time you duplicated it As a note, when you duplicate a workbook, the source does not get duplicated. You'll have to go in and add it in again. Original Workbook
(217 kB)
Duplicated workbook:
(159 kB)
Let me know if that makes sense
Laurent Baillot
·
·
this is the original notebook. All the links disappear upon duplication
LuisArturo (Clay)
·
·
Hey there J thanks for reaching out, how can we help you?
Laurent Baillot
·
·
hi, the bug is still ongoing. waiting for Smit (Clay) to share a solution from engineering https://clayrunhq.slack.com/archives/C025KSBLPGX/p1752771718771289?thread_ts=1752701103.975539&cid=C025KSBLPGX
Clay
APP
·
·
Hi J, Thanks for reaching out to support. Our engineering team is actively working to fix this issue. We appreciate your patience. -Nicole
Nicole Goot
·
·
Good news! Happy to report that we heard back from the team and this issue should be fixed. Try a quick refresh (Cmd/Ctrl + Shift + R) and let us know if the problem has been resolved on your end, or if you still have trouble. Thank you for your patience as we worked on it.