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 (Clay)
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
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.
.png){kind=logo}
