.png){kind=logo}
Troubleshooting Error Writing to Database Table
Hi. Error writing to table. Actions taken so far
deleted destination table and rebuilt
renames destination table
deleted and rebuilt enrichment.
If you're still experiencing the "Error writing to table" issue after your attempts, try these additional steps: 1. Use the Force Run option in the table settings. This may take some time depending on your table size. 2. If the issue persists: • Delete the affected column • Create a fresh column • Re-map your data to the write to table integration (ensure auto-dedup is activated in the other table) 3. Check your Clay API key: • Go to Settings > Connections • Search for Clay • Ensure the API key is correctly configured If these steps don't resolve the issue, you may need to request human assistance for further troubleshooting.
Charles - Do you mind sending the link (url) to the table so we can take a look?
(52 kB)
Mark L.··Charles, thanks for sharing the screenshots and the link. If you run individual cells in those columns, do you see anything amiss? (I would have tested, but didn't want to interrupt any workflows downstream!) I'd be curious whether or not the column actual works for the selected tables in the settings. Based on the error message... "Failed to load table ID t_wGmr8rBzxHAb with error: NotFound: Table t_wGmr8rBzxHAb does not exist" ...it is accurate. This table does not in fact exist: https://app.clay.com/workspaces/455133/workbooks/wb_qNddQYUJXcWw/tables/t_wGmr8rBzxHAb Do you recall deleting any tables in this workbook earlier? I'm wondering if somehow the list in the WTT action is wrongly "remembering" a table that used to exist, but doesn't any longer.
Hey Mark, give me a min
I did delete a table where the initial write to table was pointing to. I delete it as it wasn't writing to table. I then created a new table (with the same name) - similar problem. So, I deleted the table, created a new one, with a modified name, you'll notice the '-'. I then delete the enrichment in the original file and reran - which is where we are now.
Feel free to run the column. Nothing will break.
- Mark L.··
I think I've managed to resolve this. In this table "Founder [company + people]", I set up a new WTT action called "Clay Test". A https://app.clay.com/workspaces/455133/workbooks/wb_qNddQYUJXcWw/tables/t_pZVYyBmZ2qzJ/views/gv_w63zxiprPBKg What I noticed is that this other "Founder [-people]" table here still has a partially-completed "stub" column, pointing to the deleted table. B https://app.clay.com/workspaces/455133/workbooks/wb_qNddQYUJXcWw/tables/t_snzACqNSZDb6/views/gv_zg6GVTfCaSbj Because A was writing to B, and B was writing C (deleted table), the error was being messageed "upstream", so to speak. Having updated B, my Clay Test and the other WTT columns looked okay after re-saving them – no more error displaying. I re-ran the first one, where all the fields were mapped, and that appeared to work out okay. Everything look good to you?