Troubleshooting 'Write to Other Table' Column Stuck in Queue

Hi. One of my 'write to other table' columns is not working; it's been 'queued' for hours now. Can someone help me figure out why? Column name = 'Write to All Jobs' Table = https://app.clay.com/workspaces/356594/workbooks/wb_xeVTS97Hh9Ms/tables/t_6kvdhMNUJWqb/views/gv_6TNGD7f5xaE7 Table it should write to = https://app.clay.com/workspaces/356594/workbooks/wb_xeVTS97Hh9Ms/tables/t_EoFWUu4yvhJB/views/gv_Ufg7VhuXKmAD

5 comments

Channeled
APP
·
·
To resolve the queued status issue with your 'Write to All Jobs' column, you can try these troubleshooting steps: 1. First, try to force run the column: • Right-click on the column • Hover over "Run Column" • Select "Force Run All Rows"If that doesn't resolve the issue, check these common causes: 1. Verify your column configuration: • Ensure all mapped columns exist in both tables • Confirm that the destination table is correctly selected • Double-check that all columns are properly mapped 2. Check your Clay API key: • Make sure your API credentials are valid • Verify there are no authentication issues with your accountIf the issue persists after trying these steps, you should request help from a human agent in this conversation. Sources: Write to table integration overview | Documentation | Clay University Run Options
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!
Bo (.
·
·
This issue occurs when an enrichment is blocked due to multiple stop/start cycles. To resolve it, duplicate the column and run it again. Use auto-dedupe in the destination table to prevent duplicates. Simply click on the column header, duplicate it, and then activate auto-dedupe in table B. Let me know if you need assistance with the column setup or deduplication settings.
Nicolas P.
·
·
Got it, thanks!
Channeled
APP
·
·
Hi Nicolas P.! This thread was recently closed by our Support team. If you have a moment, please share your feedback: