Bug Report: Issues with 'Write to Other Table' Enrichment in Clay System | Clay

Bug Report: Issues with 'Write to Other Table' Enrichment in Clay System

Hello Clay Team, I'm really loving this system. I took a one year hiatus, and just came back to it and am blown away! One bug that I came across is regarding the 'Write to Other Table' enrichment. I have a sheet of 2,709 rows of data in a workbook. I created a second sheet for additional enrichment to these records, however, only 2,650 of them transferred over. I can't figure out why. I used the 'Lookup Single Row in Other Table' enrichment to determine which were the 59 that were left behind. I then used another 'Write to Other Table' process on those 59 to send to a third sheet... but this time only 14 transferred to the 3rd sheet. Any idea why this is happening? Thank you.

9 comments

Channeled
APP
·
·
If you're experiencing issues with rows not transferring when using the Write to Table feature, this is likely due to an API key configuration issue. To resolve this: 1. Go to Settings > Connections 2. Search for "Clay" in the connections 3. Verify that your Clay API key is properly connectedFor optimal performance when using Write to Table, ensure you have: ** A properly configured source table to copy data from ** A destination table with named columns * A valid Clay API keyIf you've confirmed these settings and are still experiencing issues, you may want to check if you have any conditional run settings enabled that might be preventing certain rows from transferring.If you need further assistance with this issue, please request human assistance by clicking on "Talk to a person". They'll be able to investigate your specific case in more detail. Source: Write to Table - Clay University
Channeled
APP
·
·
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!
Stephen S.
·
·
Thanks, but my API key is fine, and there are no conditional run settings that would interfere with this process.
Daniel K.
·
·
Hi Stephen! Do you mind sending the link to the table so we can take a look? https://downloads.intercomcdn.com/i/o/1171717996/ac7729f84b426e1d0358af02/image.png?expires=1733148000&signature=cbd3412df62ab810e3c0dd0859ed35db91a0ed0fb301289a2d57c2b99a95ef54&req=dSEgF85%2FmohWX%2FMW1HO4zYTywSj9Ap8W2BKsam%2FhVPv5Bg%3D%3D%0A
Stephen S.
·
·
Hi Daniel, Sure thing, here is the link to the workbook: https://app.clay.com/workspaces/25609/workbooks/wb_bPNPUvWZuRjd/tables/t_nNNU4fGRweBZ/views/gv_2VCZStN6iTY6 Only transferred 2650 of 2709 from table "1" to table "2". For table "2.A." -- I isolated the 59 that didn't transfer from table 1, and tried again. I was only able to then transfer 14 of the 59. Thank you!
Daniel K.
·
·
Hey Stephen, looking at this. I need to investigate a bit more. I'll get back to you soon! Thanks for your patience here.
Channeled
APP
·
·
Hi Stephen S.! This thread was recently closed by our Support team. If you have a moment, please share your feedback:
Channeled
APP
·
·
Thanks! We've reopened this thread. You can continue to add more detail directly in this thread.
1
Channeled
APP
·
·
Hi Stephen S.! This thread was recently closed by our Support team. If you have a moment, please share your feedback: