What causes TIME_TRAVEL_OUT_OF_RANGE?

The DATA_RETENTION_TIME_IN_DAYS setting for the table is set to 0 (disables Time Travel) or a short value. The requested AT or BEFORE timestamp is older than the retention period. The retention period was reduced after the data was written, making older versions inaccessible. Using a negative OFFSET in AT(OFFSET => -N) that exceeds the retention duration in seconds. Cloning or restoring a table while specifying a timestamp older than the retention window

How do I fix TIME_TRAVEL_OUT_OF_RANGE?

Check the current retention period: SHOW TABLES LIKE 'my_table' — see DATA_RETENTION_TIME. Increase retention for the table: ALTER TABLE my_table SET DATA_RETENTION_TIME_IN_DAYS = 14. For Snowflake Enterprise, retention can be up to 90 days; for Standard, maximum is 1 day. If the historical version is needed and retention has lapsed, check if a clone or backup exists. Avoid setting DATA_RETENTION_TIME_IN_DAYS = 0 on tables that may need recovery — use 1 day minimum

Medium severityexecution

Power BI Refresh Error:
TIME_TRAVEL_OUT_OF_RANGE

What does this error mean?

The requested Time Travel timestamp or offset falls outside the retention period for the table or schema. Snowflake cannot reconstruct the historical version of the data because the retention window has passed.

Common causes

1The DATA_RETENTION_TIME_IN_DAYS setting for the table is set to 0 (disables Time Travel) or a short value
2The requested AT or BEFORE timestamp is older than the retention period
3The retention period was reduced after the data was written, making older versions inaccessible
4Using a negative OFFSET in AT(OFFSET => -N) that exceeds the retention duration in seconds
5Cloning or restoring a table while specifying a timestamp older than the retention window

How to fix it

1Check the current retention period: SHOW TABLES LIKE 'my_table' — see DATA_RETENTION_TIME
2Increase retention for the table: ALTER TABLE my_table SET DATA_RETENTION_TIME_IN_DAYS = 14
3For Snowflake Enterprise, retention can be up to 90 days; for Standard, maximum is 1 day
4If the historical version is needed and retention has lapsed, check if a clone or backup exists
5Avoid setting DATA_RETENTION_TIME_IN_DAYS = 0 on tables that may need recovery — use 1 day minimum

Frequently asked questions

What is the difference between Time Travel and Fail-Safe?

Time Travel is user-accessible for 0–90 days (plan-dependent) and supports AT/BEFORE queries and UNDROP. Fail-Safe is a 7-day Snowflake-managed disaster recovery window after Time Travel expires — it is only accessible by Snowflake Support, not end users.

Does increasing DATA_RETENTION_TIME_IN_DAYS increase storage costs?

Yes — Snowflake charges for Time Travel storage at the same rate as active storage. For large, frequently updated tables, longer retention can significantly increase your storage bill.