MetricSign
EN|NLRequest Access
High severityexecution

Power BI Refresh Error:
COPY INTO (Stage Not Found)

What does this error mean?

The COPY INTO command cannot locate the specified stage. The stage name is invalid, the stage was dropped, or the executing role lacks USAGE privilege on the stage.

Common causes

  • 1Stage name is misspelled or uses the wrong prefix (@myschema.mystage vs @mystage)
  • 2The stage was dropped or belongs to a different schema than the current session context
  • 3The executing role lacks USAGE privilege on the stage
  • 4An external stage's cloud storage URL or credentials were changed, causing Snowflake to mark it invalid
  • 5The stage was created in a different Snowflake account or database

How to fix it

  1. 1List available stages: SHOW STAGES IN SCHEMA mydb.myschema
  2. 2Use a fully-qualified stage reference: @mydb.myschema.mystage
  3. 3Grant USAGE on the stage to the executing role: GRANT USAGE ON STAGE mydb.myschema.mystage TO ROLE my_role
  4. 4For external stages, verify cloud storage credentials are still valid: DESC STAGE @mydb.myschema.mystage
  5. 5If the stage was accidentally dropped, recreate it with the original storage URL and credentials

Frequently asked questions

What is the difference between an internal and external stage in Snowflake?

Internal stages store files within Snowflake's managed storage. External stages point to cloud storage (S3, Azure Blob, GCS) you control. External stages require valid cloud credentials and can fail independently of Snowflake if those credentials expire.

Can I recover files from a dropped internal stage?

No — dropping an internal stage permanently deletes the staged files. Unlike tables, stages are not covered by Time Travel. Ensure critical staging areas are protected from accidental drops with appropriate access controls.

Other execution errors