Recalculating a spreadsheet is different from receiving a fresh external observation. Identify the data source and its refresh mechanism before treating the visible result as current.
Check each freshness boundary
Inspect the original publisher or source file, then any connector or intermediate spreadsheet, then the final formula. Record where the latest known source value first differs from the report.
A dashboard timestamp produced by NOW only describes its own calculation time. It does not prove that every imported record was fetched at that moment.
Use the relevant import guidance
Google documents periodic checks for import functions and warns that reopening or refreshing the browser does not necessarily trigger a source refresh. Dedicated and general guides differ on some IMPORTRANGE interval details, so avoid promising an exact refresh deadline.
Review throttling, access prompts, errors, and chained dependencies. Do not add a rapidly changing volatile argument as a universal refresh trick; import functions restrict volatile dependencies and repeated calls can create additional load.
Report stale data honestly
Compare a source record and its official update time with the imported result. Keep last-known data only when appropriate and label its age. Separate a failed check from a confirmed unchanged source.
If an operational decision requires a guaranteed collection schedule, use an authorized ingestion method with explicit fetch logs, validation, and failure reporting. A normal formula-based import may not meet that requirement. Preserve existing data while investigating, and avoid rebuilding every formula or changing unrelated network settings. Establishing freshness requires evidence from the source boundary, not merely a responsive spreadsheet or a recent local recalculation.
References
Reviewed against the linked official product guidance on November 3, 2026. Features, limits, screen labels, and access can vary by account, platform, region, and organization policy.