.png&w=3840&q=75){kind=logo}
Marking Cells as Not Stale in Spreadsheet Applications
Is there a way to mark cells as "not stale" without having to re-run them? I changed an input cell that affected almost all my rows. The sheet thinks they're stale but they are not in reality.
Yes, you can handle this situation by using the Auto-update controls. When you click the Auto-update icon at the bottom right of your table, select "Continue without running" instead of "Update cells." This will allow you to mark the cells as not stale without triggering a re-run of the enrichments. Source: Auto-update and Auto-dedupe Table
This did not work unfortunately
I apologize for the inconvenience; would you like to rephrase your question or speak with our support team for further assistance?
person
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 (.··Hey there! Let me clarify something about how staleness works in Clay: Staleness is actually an automatic system feature - it's not something we can manually override. Could you tell me more about what changes you made to your input cell? That way I can better understand your situation and maybe suggest a more efficient way to handle your updates. 🤔 For example: - What type of input did you change? - Which columns are showing up as stale? This will help me give you the most relevant solution! 😊
https://app.clay.com/workspaces/423342/workbooks/wb_2yzrNp8cphiU/tables/t_94MukWzWgDtd/views/gv_Nvp2JRE56vSD The rows in "Email Finder" were originally linked to a contact sheet that I duplicated. I then re-linked the rows to the new (i.e. duplicated) contact sheet which made most of my rows in "Email Finder" stale, even though the data was actually the same (i.e. same contacts, just from a different sheet)
My gut says no way to fix it but let me know what you think
- Bo (.··
Yes, but it's stale because it's not the same version! It's another version, although it's the "same," it's not the same column. The only way to fix this is to re-run the rows unfortunately!
got it -- thanks