An IMPORTRANGE result can lag because of source access, upstream calculations, throttling, or a chain of receiving files. Diagnose the path before rebuilding the import.
Check the source directly
Open the exact source with the intended account and confirm the expected value is already saved there. Inspect the source range, tab name, and any error in the destination formula.
If the source owner changed or the granting user’s access was removed, review authorization through the normal owner-approved process. Do not widen public sharing to restore an import.
Trace intermediate spreadsheets
If C imports from B and B imports from A, inspect A, B, and C separately. An upstream calculation or import delay can propagate through the chain, so C’s local recalculation does not necessarily fetch a new original observation.
Google’s guides describe periodic refresh and propagation delays; dedicated IMPORTRANGE guidance and general calculation guidance differ in their stated refresh intervals. Do not promise a fixed real-time delivery deadline.
Reduce repeated requests and verify freshness
Limit imported ranges and unnecessary receiving files. Avoid circular imports and rapidly changing formula arguments. Repeatedly deleting and recreating formulas can add load rather than resolve an upstream cause.
Compare a known source record and its update time with each receiving stage. Preserve a last-known snapshot when appropriate, clearly labeled as stale rather than current. If the workflow requires guaranteed delivery or auditable scheduled refresh, choose an authorized ingestion design with explicit logging and validation. A visible green loading bar or a refreshed browser tab is not sufficient evidence that the latest source data reached the final report.
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.