> For the complete documentation index, see [llms.txt](https://docs.paradime.io/app-help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.paradime.io/app-help/get-help/error-list/workspace-and-warehouse-errors.md).

# Workspace and warehouse errors

Use this page for errors tied to connections, warehouse metadata, or local workspace state.

### PARA-1000: Missing production warehouse connection

This error appears when you run a production dbt job in Bolt without an active production warehouse connection.

It also appears when your production run references a target that does not exist.

{% hint style="success" %}
**Solution**

* Add an active production connection for the scheduler.
* Confirm the connection works before rerunning.
* If you use a custom target, confirm that target exists.

See [Setting Up Data Warehouse Connections](/app-help/guides/paradime-101/getting-started-with-your-paradime-workspace/setting-up-data-warehouse-connections.md) and [Scheduler environment](/app-help/documentation/settings/connections/scheduler-environment.md).
{% endhint %}

### PARA-1007: Couldn't fetch info-schema from Snowflake for production catalog

Paradime could not fetch the information schema for your production catalog.

Common causes include:

* The production user does not exist.
* The stored credentials are invalid.
* The Snowflake account no longer exists or has expired.

{% hint style="success" %}
**Solution**

Check the production connection details.

Test the connection again.

If the test fails, confirm the credentials with your Snowflake admin.

See [Snowflake](/app-help/documentation/settings/connections/scheduler-environment/snowflake.md).
{% endhint %}

### PARA-1007: Couldn't fetch info-schema from Snowflake for dev catalog

Paradime could not fetch the information schema for your development catalog.

Common causes include:

* The development user does not exist.
* The stored credentials are invalid.
* The Snowflake account no longer exists or has expired.

{% hint style="success" %}
**Solution**

Check the development connection details.

Test the connection again.

If the test fails, confirm the credentials with your Snowflake admin.

See [Snowflake](/app-help/documentation/settings/connections/development-environment/snowflake.md).
{% endhint %}

### PARA-1014: Couldn't list databases when running `paradime sources generate`

Paradime could not list databases to generate `sources.yml`.

This usually means your development connection does not have enough access to query information schema.

{% hint style="success" %}
**Solution**

Review the permissions on your development connection.

Then check the setup guide for your warehouse in [Code IDE environment](/app-help/documentation/settings/connections/development-environment.md).
{% endhint %}

### PARA-1015: Clear Paradime local storage

Some UI issues come from stale local browser data.

For the full reset steps, see [Clear Paradime local storage](/app-help/get-help/error-list/clear-paradime-local-storage.md).


---

# 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://docs.paradime.io/app-help/get-help/error-list/workspace-and-warehouse-errors.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.