Stopping a run fried a column.
Already solved it by duplication and re-referencing but wanted to point you to this (Bo (. we had this case last week in a different workspace)
To prevent columns from being affected during runs, here are some best practices:
1. Test your enrichments on a small scale first:
• Run on just the first 10 rows to verify everything works as expected
2. Control auto-updates:
• Turn off auto-update while building and testing your table
• You can disable this at the table level by clicking the three dots next to your table name and selecting "Auto-Update Columns"
3. Use controlled run options:
• Run on a specific number of rows
• Use "Run First 10 Columns" when testing
• Choose "Run All Rows that haven't run or have errors" instead of forcing runs on all rows
These precautions help ensure your data remains intact while testing and running enrichments.
Hey Andreas! Sorry that it's happening in 2 tables.
You're right - filtering for stale is the way to go here since formulas won't work in this case. Once you're in this view, you can click on the column header > run column > run all rows (that'll run the rows in this view) make sure to have auto-dedupe on. I've added the new tables you mentioned to our previous bugs about this.
Let me know if you need anything else!
.png){kind=logo}
