Issue with Sending Data to Other Tables in Workbook

Robert I. · 2025-11-11 16:26:43.67021+00

Bug. Can't send data to other tables within my own workbook for some reason.

Issue with Sending Data to Other Tables in Workbook | Clay

8 comments

· Sorted by Oldest

Clay Support
APP
·
·
The "No resources found" issue when trying to select a destination table can occur due to several reasons: [1]
Potential causes:
Maximum table limit reached: There's a maximum of 10 tables that can be connected via write to table actions across workbooks [2]
Linear direction constraint: Data can only flow in one direction (A → B → C), not in loops
Misconfigured integrations: Invalid or conflicting data, such as writing to deleted columns or tables with circular references
To fix this:
1.
Try using Force Run in your table settings
2.
Delete the affected column and create a fresh one
3.
Re-map your data to the write to table action
4.
Consider using the newer "Send table data" action instead, as "write to table" has been deprecated
You can click into the specific cell where you're seeing the error to get more details about what's causing the issue.
Clay Support
APP
·
·
Was that helpful?
Robert I.
·
·
Still not working. None of those potential causes are the case here. None of those fixes work in this case because I can't even select a table to send the data to. Just shows No resources found
Clay Support
APP
·
·
I'm sorry for the trouble you're experiencing. I'll connect you to a human agent who can assist you further with this issue.
Clay Support
APP
·
·
Our support team has got your message and we'll get back to you soon!
If you’re dealing with a specific table, drop the URL below so we can help you quicker. Otherwise, someone from our team will be in touch soon!
image.png(93 kB)
Robert I.
·
·
https://app.clay.com/workspaces/12457/workbooks/wb_0t5f36uzSBNBSb6RqhM/tables/t_0t5kkjsS7GfZKaCeThS/views/gv_0t5kkjsxaFUkZYVCtjJ
Andrew Q.
·
·
Robert - Sorry for this, it looks like we've got a bug on our hands. I've escalated this to our engineering team to help look into it. We'll follow up here as soon as we know more!
1
Andrew Q.
·
·
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 Support
APP
·
·
The "No resources found" issue when trying to select a destination table can occur due to several reasons: [1]
Potential causes:
Maximum table limit reached: There's a maximum of 10 tables that can be connected via write to table actions across workbooks [2]
Linear direction constraint: Data can only flow in one direction (A → B → C), not in loops
Misconfigured integrations: Invalid or conflicting data, such as writing to deleted columns or tables with circular references
To fix this:
1.
Try using Force Run in your table settings
2.
Delete the affected column and create a fresh one
3.
Re-map your data to the write to table action
4.
Consider using the newer "Send table data" action instead, as "write to table" has been deprecated
You can click into the specific cell where you're seeing the error to get more details about what's causing the issue.
Clay Support
APP
·
·
Was that helpful?
Robert I.
·
·
Still not working. None of those potential causes are the case here. None of those fixes work in this case because I can't even select a table to send the data to. Just shows No resources found
Clay Support
APP
·
·
I'm sorry for the trouble you're experiencing. I'll connect you to a human agent who can assist you further with this issue.
Clay Support
APP
·
·
Our support team has got your message and we'll get back to you soon!
If you’re dealing with a specific table, drop the URL below so we can help you quicker. Otherwise, someone from our team will be in touch soon!
image.png(93 kB)
Robert I.
·
·
https://app.clay.com/workspaces/12457/workbooks/wb_0t5f36uzSBNBSb6RqhM/tables/t_0t5kkjsS7GfZKaCeThS/views/gv_0t5kkjsxaFUkZYVCtjJ
Andrew Q.
·
·
Robert - Sorry for this, it looks like we've got a bug on our hands. I've escalated this to our engineering team to help look into it. We'll follow up here as soon as we know more!
1
Andrew Q.
·
·
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.