Hey, some of our team are reporting much slower than normal performance when using templates for verification. some tables taking hours to complete. These are workbooks where 'Write to Table' is stuck on 'queued' status Workspace: 12893
There could be several factors causing the slower performance with templates. Here are some steps to help address the processing delays:1. Check if your search queries are specific and well-defined 2. Try breaking down your large data requests into smaller batches 3. Review your usage limits, tiers and API quotas 4. Verify your network connection stabilityIf these steps don't resolve the issue and the performance issues persist, you should request help from a human agent who can investigate the specific details of your workspace.
The issue is primarily to do with Clay columns such as write to other table: https://app.clay.com/workspaces/12893/workbooks/wb_p5NCtTmmxSZg/tables/t_MfKSSAaD5wy7/views/gv_BwAAubQB7xBc
The information I've found doesn't directly address slow performance issues with the "Write to Other Table" feature when using templates for verification. However, I can provide some general insights about this feature.The "Write to Other Table" action in Clay allows users to transfer data between tables, which can be useful for consolidating information or creating automated workflows. This feature supports writing lists, single values, or objects, providing flexibility in data transfer.If you're experiencing slow performance, it could be related to the amount of data being transferred or how the templates are set up. To help troubleshoot this issue, could you provide more details about the size of your tables and the specific steps in your verification process using templates? Sources: Write to Other Table with Clay Labs Write to table integration overview | Clay University
Looks like you're still looking for help. We're escalating this over to our support team and someone should be in touch soon. In the meantime, feel free to include any other information that may be helpful in solving your issue!
Support to get higher bandwidth would be massively helpful to us. We're scaling out clay with the view to ensure we can continue growing the account and desire to move to enterprise licensing across next year. Our team need faster turn around and currently the wait time on things like 'write to table' is extremely slow, reporting to me they are taking multiple hours. We've got a peak demand t complete data work ahead of Friday. These tables are examples: https://app.clay.com/workspaces/12893/workbooks/wb_bt5Fi8mwquuh/tables/t_ET5ux4omuxt2/views/gv_6BW5AwSY4dDB https://app.clay.com/workspaces/12893/workbooks/wb_8YQjtfi4n5hp/tables/t_mSwG9EZDV7UP/views/gv_RtzTUoCuqYoz https://app.clay.com/workspaces/12893/workbooks/wb_iz7sUddrqd7R/tables/t_PJbQy4TsvbMd/views/gv_Gp5isT5CfnaW https://app.clay.com/workspaces/12893/workbooks/wb_oRRGHqn9ftBC/tables/t_AfEC36qqQKyz/views/gv_dZmZZDKBiCZB https://app.clay.com/workspaces/12893/workbooks/wb_YFJZiH7gGPmv/tables/t_AhTTCqUMyf6q/views/gv_AVQdcBrR4jmY https://app.clay.com/workspaces/12893/workbooks/wb_8mVXrKxXJJyK/tables/t_TRZrz5zA8uVs/views/gv_hZry2gWrXSYY https://app.clay.com/workspaces/12893/workbooks/wb_nCgz3vNZqQjY/tables/t_SEhc8hEzpZEx/views/gv_ddVf9aCjJort https://app.clay.com/workspaces/12893/workbooks/wb_Wg4kcwFZPqxg/tables/t_oE34tZJkwEAN/views/gv_9yZd6us5fMSw https://app.clay.com/workspaces/12893/workbooks/wb_p5NCtTmmxSZg/tables/t_MfKSSAaD5wy7/views/gv_BwAAubQB7xBc
It seems these tables are all just stuck, there's no progress happening
I had the same issue, with Write to Table being extremely, unusably slow. I timed it and it was processing avg 17 rows per minute. The speed normalized after ~18 hours to avg 138 rows per minute. We never got to the root issue but if this is happening for other folks as well, I hope that the Clay team will take a closer look at it. Clay was basically unusable during those 18 hours. Cc: Bo (.
Signing off and have resorted to a work around for the teams for the meantime. really i need of some clarity on whether workbooks are actually scalable, if write to table just falls over / runs really slow when it's used more than a certain amount in parallel, or, is this something that can be fixed?
Hey there! Really sorry for the delay. We're looking into this and will get back as soon as we have an update🙏🏽.
Thanks Daniela
sharing for example, 8 hours later some of the tables still not progressed
Hey, thanks for reaching out JB - We've reached out to our team, but if you're running multiple write to table at the same time, this is what will be causing this. If there's also multiple re-run of the column, that can make them in this weird stale state, and creating a new one will fix this. We'll give you an update when we get one from the team :)
ty
If this is a known cause for slowing down, is it 'normal' for tables to take over a day to catch up? I'm questioning whether they are actually queued or if it's just frozen. Hope this can be resolved as it's quite a critical column we want to use at scale in SOPs. with multiple teams using workbooks for batch data processing in parallel.
Hey Joel. Really sorry about this. It looks like your tables were updating but were running slow due to the workspace rate limit for the write to other table integration. If the integration is running for thousand rows across different tables it could take much longer for cells to finish updating. Could you confirm how many tables were running that action at the time? Is it the list of tables shared above? We'll check that with the team.
https://app.clay.com/workspaces/12893/workbooks/wb_p5NCtTmmxSZg/tables/t_MfKSSAaD5wy7/views/gv_BwAAubQB7xBc https://app.clay.com/workspaces/12893/workbooks/wb_Wg4kcwFZPqxg/tables/t_oE34tZJkwEAN/views/gv_9yZd6us5fMSw https://app.clay.com/workspaces/12893/workbooks/wb_nCgz3vNZqQjY/tables/t_SEhc8hEzpZEx/views/gv_ddVf9aCjJort https://app.clay.com/workspaces/12893/workbooks/wb_8mVXrKxXJJyK/tables/t_TRZrz5zA8uVs/views/gv_hZry2gWrXSYY https://app.clay.com/workspaces/12893/workbooks/wb_YFJZiH7gGPmv/tables/t_AhTTCqUMyf6q/views/gv_AVQdcBrR4jmY https://app.clay.com/workspaces/12893/workbooks/wb_oRRGHqn9ftBC/tables/t_AfEC36qqQKyz/views/gv_dZmZZDKBiCZB https://app.clay.com/workspaces/12893/workbooks/wb_iz7sUddrqd7R/tables/t_PJbQy4TsvbMd/views/gv_Gp5isT5CfnaW https://app.clay.com/workspaces/12893/workbooks/wb_8YQjtfi4n5hp/tables/t_mSwG9EZDV7UP/views/gv_RtzTUoCuqYoz https://app.clay.com/workspaces/12893/workbooks/wb_bt5Fi8mwquuh/tables/t_ET5ux4omuxt2/views/gv_6BW5AwSY4dDB https://app.clay.com/workspaces/12893/workbooks/wb_2VAS4F6iZavm/tables/t_zVXshg2VWFC4/views/gv_bJM8wfRUjV5r https://app.clay.com/workspaces/12893/workbooks/wb_mmD4z5DeRTnv/tables/t_EAxYs4UPHFfB/views/gv_jrDukVmZMqbo https://app.clay.com/workspaces/12893/workbooks/wb_bzhbeAJr5USa/tables/t_nwfttrZHuxvb/views/gv_WZoperRk8Ss3 https://app.clay.com/workspaces/12893/workbooks/wb_tNeb9WYxfigY/tables/t_bXmtx6rGN9KH/views/gv_buns2HJGk8w6 https://app.clay.com/workspaces/12893/workbooks/wb_65AhvdJjgZUq/tables/t_CpGpiJ4q7Q3k/views/gv_mupev9VYWbpr https://app.clay.com/workspaces/12893/workbooks/wb_XuNAvPtgfMd7/tables/t_t2ZvMtnQavA5/views/gv_UnsgW9pHD6UV https://app.clay.com/workspaces/12893/workbooks/wb_86Ma3sxKtfUB/tables/t_pbGaPzta3YY3/views/gv_QWJ5uU9S6aeM https://app.clay.com/workspaces/12893/workbooks/wb_QPp2pqrVWme8/tables/t_HKEMWuy8rB9v/views/gv_MNEQuF42YoDE https://app.clay.com/workspaces/12893/workbooks/wb_nsX8iyQZQgCk/tables/t_Q33v4ococ8cT/views/gv_p9xw8QAZq675 https://app.clay.com/workspaces/12893/workbooks/wb_CzbyUYnqftC2/tables/t_wfxn7wqghMnG/views/gv_CEu9dCT5hiXX https://app.clay.com/workspaces/12893/workbooks/wb_dweNDDi7nkMU https://app.clay.com/workspaces/12893/workbooks/wb_78cCRGybjJSB/tables/t_Y9aFhPVWkhNj/views/gv_nEVzvCoXF3ai
Appreciate this is a lot, but we want to use clay a lot and write to table specifically in SOPs. If rate limits can be lifted it would be a significantly positive impact to our roll out.
Joel B. Im curious, did your team just roll out these SOPs with a lot of Write to Tables? Ive been using Clay everyday for the past year and always used a lot of Write to Tables, and the lag just started this week for me. Wondering the timing of both our issues is a coincidence or if Clay rolled out its rate limit recently.
It's recent for us yeah, just rolled out SOPs this week, so the function usage is at a higher than previous norm. I've been aggressive with high volume processing in previous role and never known it to be this slow.
except back in the early days
Yeah same - Ive always incorporated Write to Tables as a pseudo relational database lookup and also a pseudo function in my workflows so been using it heavily for a while now. Just started noticing this week so the timing is interesting. If Clay didnt roll out the rate limits this week and theyve actually been in place for a while, I wonder if its due to a bug. Bo (. did the rate limits roll out this week?
yeah I used to use it in a much more layered fashion within tables at higher volume, with big batches in parrallel, than we are with this SOP, with no issue.
it got slower, but it didn't stop like this
Hi J, thanks for reaching out. Unfortunately, we've noticed that the "write to other table" command has been running slowly recently. We've already discussed this with our engineers, and they're working on a fix. This issue shouldn’t continue in the long-term, and I apologize for the inconvenience it’s causing you.
Thanks Stefano, appreciate the update. It would be great if we can be notified when the fix is implemented. Happy to feedback on our experience once it is.
Hey, wondering if there is any updates on this? facing low run speeds again today.
Hello. The write to other table issue should have been fixed. The reason many of the cells are showing as "Queued" is due to our batching process. We process rows in batches, typically executing around 60 rows at a time. Once a batch completes, the next set of rows is processed. This is why you'll see the "Queued" status—these rows are lined up to run next. This is not an error, but simply part of the system's process to handle data efficiently. Depending on the volume of data you're working with, it can take some time for all the rows to be processed, but rest assured the system is working through them as quickly as possible. Let me know if you have any further questions or need assistance with anything else!
Thanks, seemed to be a caching issue in the end, rows showed queued status that were finished.
.png&w=3840&q=75){kind=logo}
