Issue with Writing to a Table in Workbook - Assistance Needed

Henry J. · 2024-09-26 22:16:20.862431+00

Hi team - please can someone take a look at this table for me and work out why I can't write to the other table in that workbook?

Issue with Writing to a Table in Workbook - Assistance Needed | Clay

8 comments

· Sorted by Oldest

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!
Bo (.
·
·
Let me check with the engineer to confirm if there’s anything we can do, but based on past experience, this issue usually happens when the data consumption from writing to the table becomes too high after 4-5 iterations, especially when there’s a lot of data in your workbooks all at once. It might be better to do more steps via tables and fewer via workbooks to optimize the process, but I’ve flagged this to the team for further review. I’ll keep you posted! 😊
Henry J.
·
·
Thank you - please let me know! I thought workbooks would have the same compute power as a series of tables, but is it more that one workbook = same power as one table?
Henry J.
·
·
And it is possible to take a table from a workbook and make it a standalone table? Or it can only be moved to another workbook?
Henry J.
·
·
I just deleted a bunch of the "write to tables" and moved some tables into a different workbook, but it's still throwing up the same error (now for all of the tables, not just the one I pinged you about earlier). Any clues as to how the logic behind the error message works?
Bruno R.
·
·
Hi Henry, thanks for reaching out and sorry that this issue is persisting. I don't think what Bo was mentioning was related to compute here, but rather to Clay API rate limits which you may run into if your running many write to table enrichments concurrently across multiple streaming table setups. The engineering team is currently is investigating this issue and we'll be able to provide you with more context as soon as we know more. Thank you for your patience! Could you also add some context on the exact table where you're experiencing this issue? It looks like all the write to table enrichment columns in the workbook you shared above are running correctly.
Channeled
APP
·
·
We haven't heard back from you in a bit, so we're going to go ahead and close things out here - feel free to let us know if you still need something!
Channeled
APP
·
·
Hi Henry J.! This thread was recently closed by our Support team. If you have a moment, please share your feedback:

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!
Bo (.
·
·
Let me check with the engineer to confirm if there’s anything we can do, but based on past experience, this issue usually happens when the data consumption from writing to the table becomes too high after 4-5 iterations, especially when there’s a lot of data in your workbooks all at once. It might be better to do more steps via tables and fewer via workbooks to optimize the process, but I’ve flagged this to the team for further review. I’ll keep you posted! 😊
Henry J.
·
·
Thank you - please let me know! I thought workbooks would have the same compute power as a series of tables, but is it more that one workbook = same power as one table?
Henry J.
·
·
And it is possible to take a table from a workbook and make it a standalone table? Or it can only be moved to another workbook?
Henry J.
·
·
I just deleted a bunch of the "write to tables" and moved some tables into a different workbook, but it's still throwing up the same error (now for all of the tables, not just the one I pinged you about earlier). Any clues as to how the logic behind the error message works?
Bruno R.
·
·
Hi Henry, thanks for reaching out and sorry that this issue is persisting. I don't think what Bo was mentioning was related to compute here, but rather to Clay API rate limits which you may run into if your running many write to table enrichments concurrently across multiple streaming table setups. The engineering team is currently is investigating this issue and we'll be able to provide you with more context as soon as we know more. Thank you for your patience! Could you also add some context on the exact table where you're experiencing this issue? It looks like all the write to table enrichment columns in the workbook you shared above are running correctly.
Channeled
APP
·
·
We haven't heard back from you in a bit, so we're going to go ahead and close things out here - feel free to let us know if you still need something!
Channeled
APP
·
·
Hi Henry J.! This thread was recently closed by our Support team. If you have a moment, please share your feedback: