Resolving Stale Data Issues in Send Table Updates

Robert J. · 2025-10-30T13:50:42.106Z

I am trying to update the data in this Send table data column by force running every row. Whenever I do this, some percentage of them get stuck in a "Stale data" state and cannot, under any circumstance, be rerun. This is just one example, but it happens ALL the time.

Resolving Stale Data Issues in Send Table Updates | Clay

Clay Support
APP
·
·
When rows show "Ran too many times, retry..." in your Send table data column, try these solutions:
Option 1: Force Rerun the Column
Click the column header
Select Force Rerun Column to reset stuck rows
Option 2: Delete and Recreate
If force rerun doesn't work:
1.
Delete the affected column
2.
Create a fresh column
3.
Re-map your data to the write-to-other table (ensure auto-dedup is activated in the destination table)
Option 3: Duplicate and Merge
Duplicate the current column
Filter for rows where the original column "is empty"
Run the new column on those filtered rows
Use the "merge columns" feature to combine results
Click into the specific cells showing errors to see more details about what's causing the issue.
Clay Support
APP
·
·
Did that answer your question?
Robert J.
·
·
If I duplicate the column and auto-dedupe, won't the new deuplicate rows get deleted? I need the new data in the old table.
Clay Support
APP
·
·
Auto-dedupe in the destination table (where you're writing data) keeps only one version of each record based on the dedupe column you select—it retains the oldest row and deletes duplicates. [1]
When you duplicate your Send table data column and run it on filtered rows (where the original column "is empty"), the new column will attempt to write those rows to your destination table. If auto-dedupe is enabled there and identifies duplicates, it will delete the newer duplicate rows, keeping the oldest. [2]
To preserve your new data: Ensure the dedupe column in your destination table uses a unique identifier that won't match between old and new records, or temporarily disable auto-dedupe while updating, then re-enable it after.
Clay Support
APP
·
·
Was that helpful?
Robert J.
·
·
But what I'm saying is the newer duplicate row would have the data that I need.
Clay Support
APP
·
·
I understand your concern about preserving the newer data in the old table. Could you please share more details about the unique identifier you are using for deduplication? This will help me better understand your setup and assist you further.
Robert J.
·
·
It could be anything. There is a unique ID field, for example.
Clay Support
APP
·
·
Thank you for the information about the unique ID field. Could you please clarify how this unique ID is currently set up in your destination table? This will help me understand how the auto-dedupe might affect your newer data and provide better guidance.
Robert J.
·
·
I literally just need to add one more column to an existing destination table. What is preventing it from just sending normally? what even is the stale data talking about?
Clay Support
APP
·
·
"Stale data" typically indicates rows that are stuck and won't rerun. This can happen due to front or backend performance issues.
To resolve stuck rows in your Send table data column:
1.
Click the column header → hover over "Run column" → select Force Rerun Column to reset the stuck rows
2.
If that doesn't work, delete the column and recreate it, then re-map your data (ensure auto-dedupe is enabled in the destination table)
Click into the specific cells showing "stale data" errors to see more details about what's causing the issue. [1]
Clay Support
APP
·
·
Did that answer your question?
Robert J.
·
·
I've already explained why neither of those will work (the issue started because I tried to Force Rerun and they got stuck in the Stale state). Here is the screenshot of the error.
Loading attachments
Clay Support
APP
·
·
I understand this is frustrating, so I’m connecting you to a human agent who can assist you further.
Intercom
APP
·
·
Clay Support is sharing a file with you.
Our support team has got your message and we'll get back to you soon!
If you’re dealing with a specific table, drop the URL below so we can help you quicker. Otherwise, someone from our team will be in touch soon!
Loading attachments

19 comments