> For the complete documentation index, see [llms.txt](https://upsolver.gitbook.io/content/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://upsolver.gitbook.io/content/support-1/error-messages/error-messages/jobs/up20010-source-data-not-found.md).

# UP20010 Source Data Not Found

A new ingestion job could not find data at the specified location. 

## Possible Causes

For example, in the bucket **stores-data**, no files were found in the **orders** folder:

```sql
CREATE SYNC JOB load_orders_raw_data_from_s3
    CONTENT_TYPE = JSON
AS COPY FROM S3 s3_connection 
    LOCATION = 's3://store-data/orders/' 
INTO default_glue_catalog.stores_data.orders_raw_data; 
```

## Possible Solutions

* Verify that the data exists at the location specified in the job.
* Verify you configured the job to read from the correct source location (topic/stream/bucket and path/etc.).
* If data is expected to arrive in the source at a later point in time, either the `SKIP_ALL_VALIDATIONS` or `SKIP_VALIDATIONS` job option should be included in the job creation declaration. This option instructs Upsolver to ignore specific validations to enable you to create a job that reads from a source that currently has no data. The validation parameter depends on the source:
  * **Amazon S3** - the source has not been created yet: `SKIP_VALIDATIONS = ('EMPTY_PATH')` 
  * **Apache Kafka** - the topic has not been created yet: `SKIP_VALIDATIONS = ('MISSING_TOPIC')` 
  * **Amazon Kinesis** - the stream has not been created yet: `SKIP_VALIDATIONS = ('MISSING_STREAM')` 
  * **Any other source:** `SKIP_VALIDATIONS = ('MISSING_DATA')`

{% hint style="info" %}
Visit the [Ingestion](/content/reference-1/sql-commands/jobs/create-job/ingestion.md) jobs reference to learn more about the `SKIP_ALL_VALIDATIONS` and  `SKIP_VALIDATIONS` job options.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://upsolver.gitbook.io/content/support-1/error-messages/error-messages/jobs/up20010-source-data-not-found.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.