MetricSign
EN|NLRequest Access
High severitydata_quality

Power BI Refresh Error:
090113 (22000)

What does this error mean?

A COPY INTO or GET command referenced a specific file on a Snowflake stage that does not exist, was already removed after a prior load, or was placed at a different path.

Common causes

  • 1The file was not uploaded to the stage before the COPY INTO command ran
  • 2The file was purged automatically after a successful prior load (PURGE = TRUE setting)
  • 3The file path pattern in the COPY INTO command does not match the actual file location
  • 4The upstream process that writes to the stage failed silently and no file was created

How to fix it

  1. 1Step 1: Run LIST @your_stage/path/ to confirm the file exists and note the exact path.
  2. 2Step 2: If the file is missing, trace the upstream process (ADF pipeline, Lambda, dbt external stage) that should have uploaded it.
  3. 3Step 3: Check the LOAD_HISTORY view to see if the file was already loaded and purged in a prior run.
  4. 4Step 4: Adjust the stage path pattern or fix the upstream upload process before retrying.

Frequently asked questions

How do I prevent accidental purging of files I still need?

Set PURGE = FALSE in your COPY INTO command, or do not enable auto-purge on the stage. You can then manually remove files after confirming a successful load.

Can I reload a file that was already purged?

Only if you still have the original source file. Re-upload it to the stage and use FORCE = TRUE in the COPY INTO command to bypass the load history deduplication check.

Other data_quality errors