For "write to table" processing issues, try these solutions: First, try Force Run: ** Right-click the column header ** Hover over "Run Column" > select "Force Run All Rows" If Force Run doesn't work: 1. Delete the affected column 2. Create a fresh column 3. Re-map your data to the write to table (ensure auto-dedup is activated in the destination table) For individual stuck cells: ** Click on the cell showing "waiting for its inputs" ** Click "re-run this cell" ** Or toggle auto-update off and on again, then accept the run prompt Alternative approach: ** Click the column header of queued cells * Hover over "Run column" > select "Force" to jump start the column These steps should resolve the processing issues without additional charges for re-running rows.
Source: Run Options
Here is example workbook https://app.clay.com/workspaces/12893/workbooks/wb_0t0xlt2sixhuymdnuvk/tables/t_0t0xlt2hWEQoeB7GKDG/views/gv_JZ5isrUc37QJ This issue can be resolved with Turning off and on auto updates of the table, but it is still an issue
Hey Teodora this is a known behavior in ‘Send to Table’ processing toggling the table’s auto-update off and back on, then accepting the run prompt, reliably resolves the issue in all reported cases so far once applied, all rows process without the need for manual re-runs this approach has been tested extensively and is a proven fix
Hello Teodora! Thanks for reaching out! Taking a look into this now.
I can see all cells under that column have run, did the turning auto update off and on fix the issue?
This message was deleted
Hey! So since you have re run the Send Table Data column, it may be tough for me to troubleshoot and identify what the root cause was. Do you have another table this is happening in? I have a bug on this I could link which i would like the eng team to take a look at. That way I can suggest best practices to ensure this does not happen again.