Hi Clay S.❤️ Good day to everyone. 🙂 Just wanted to ask again for some help to run the stale "write to other table" from this view. If possible, can you send me a loom on how can I efficiently re-run those columns. Thank you. Here is the table.
To re-run stale "write to table" columns, try using the Force Run option in your table settings - this may take time depending on table size.
If columns aren't processing correctly:
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 setup guidance, you'll need to select your destination table, choose the column with lists (if mapping lists), and map the data to your new table columns.
Unfortunately, I can't access external URLs or create Loom videos, but these steps should help resolve your stale columns.
Hi Christopher - thanks for reaching out.
Here’s a quick guide on how to re-run the stale “write to other table” cells efficiently:
Why It Shows as Stale:
This usually happens when:
** Upstream columns (like lookups, merges, or integrations) are still processing
** The input data has changed, so the downstream write action needs to refresh
** All dependent columns haven’t completed yet
How to Re-Run It:
1. Check Dependencies
Make sure all columns feeding into the “write to other table” action are fully updated (green). If any are still loading, the write action will stay stale until they’re done.
2. Manual Refresh Options
3. *Other Things to Double-Check
Once all the upstream dependencies finish updating, the stale “write to other table” cells should automatically refresh and run.
Let me know if you'd like help pinpointing which columns are holding things up!
