What causes Snowflake Clone Source Not Found?

Source object was dropped between clone request and execution. Executing role lacks SELECT or USAGE privilege on the source object. Source object name misspelled or wrong schema/database qualifier used. Trying to clone a temporary or transient table across sessions. Time-travel clone using AT/BEFORE referencing a timestamp before the object was created

How do I fix Snowflake Clone Source Not Found?

Verify the source object exists: `SHOW TABLES LIKE ' ' IN SCHEMA `. Check privileges: `SHOW GRANTS ON TABLE `. For time-travel clones, ensure the AT/BEFORE timestamp is within the retention period. Use fully qualified names: `CREATE TABLE . . CLONE . . `. If the source was recently dropped, use time travel: `CREATE TABLE t CLONE source BEFORE (STATEMENT => ' ')`

Medium severityobject management

Power BI Refresh Error:
Snowflake Clone Source Not Found

What does this error mean?

A CREATE ... CLONE statement failed because the source object (table, schema, database, or stage) does not exist or is not accessible to the executing role.

Common causes

1Source object was dropped between clone request and execution
2Executing role lacks SELECT or USAGE privilege on the source object
3Source object name misspelled or wrong schema/database qualifier used
4Trying to clone a temporary or transient table across sessions
5Time-travel clone using AT/BEFORE referencing a timestamp before the object was created

How to fix it

1Verify the source object exists: `SHOW TABLES LIKE '<name>' IN SCHEMA <schema>`
2Check privileges: `SHOW GRANTS ON TABLE <source_table>`
3For time-travel clones, ensure the AT/BEFORE timestamp is within the retention period
4Use fully qualified names: `CREATE TABLE <db>.<schema>.<clone> CLONE <db>.<schema>.<source>`
5If the source was recently dropped, use time travel: `CREATE TABLE t CLONE source BEFORE (STATEMENT => '<drop_query_id>')`

Frequently asked questions

Can I clone an object using time travel to a point before it existed?

No — time travel only applies to the object's own history. The AT/BEFORE timestamp must be within the object's DATA_RETENTION_TIME_IN_DAYS window after its creation.