> ## Documentation Index
> Fetch the complete documentation index at: https://docs.omni.co/llms.txt
> Use this file to discover all available pages before exploring further.

<AgentInstructions>

## Submitting Feedback

If you encounter incorrect, outdated, or confusing documentation on this page, submit feedback:

POST https://docs.omni.co/feedback

```json
{
  "path": "/connect-data/troubleshooting",
  "feedback": "Description of the issue"
}
```

Only submit feedback when you have something specific and actionable to report.

</AgentInstructions>

# Troubleshooting connection issues

> Diagnose and resolve common database connection errors in Omni, including cross-database queries, timeouts, and authentication.

<AccordionGroup>
  <Accordion title="PostgreSQL does not support cross-database queries">
    If you receive this error when querying a PostgreSQL database connection, it means that the query includes tables from two databases.

    While you can include multiple databases in a single Omni PostgreSQL connection, PostgreSQL itself does not allow queries that reference more than one database or cross-database joins.
  </Accordion>

  <Accordion title="Schemas missing from model">
    If you can't find a schema you included in a connection, it may be that the schema needs to be 'activated' to appear in the field browser in the workbook.

    To resolve this issue, try the following:

    <Steps>
      <Step title="Edit the schema in the model IDE">
        Open the schema in the model IDE. Add a blank space to any view in the schema and save the changes.

        Once saved, the schema should be activated and appear in the workbook's field browser.
      </Step>

      <Step title="Verify the connection's schema settings">
        If you open the model IDE but don't see the schema, the issue may be an incorrectly configured connection setting or that schemas are unknowingly being restricted.

        When the **Included schemas** setting is used, Omni will include the only specified schemas in the model. If using this field:

        1. Open the connection's settings page
        2. Verify that the schema is present
        3. Verify that the syntax is correct

        Additionally, verify that schemas aren't restricted via the model's [`ignored_schemas`](/modeling/models/ignored-schemas) parameter.
      </Step>

      <Step title="Manually query views">
        If the schema is loaded into the model but has not been activated, try manually querying views.

        In a workbook, open the **All views & fields** view in the field browser. Click the **Schema** button and select the schema from the dropdown.
      </Step>

      <Step title="Check if the view has been 'ignored'">
        If you're able to see the schema in the model IDE but are missing a specific view in the schema, it may be that the view has been [`ignored`](/modeling/views/parameters/ignored).

        1. In the model IDE, toggle the view mode to **Model**. The dropdown may default to **Combined**, so be sure to update it if needed.
        2. Navigate to the file for the view and check for an `ignored: true` parameter.
        3. Remove the parameter and promote the changes to the shared model.
      </Step>
    </Steps>
  </Accordion>
</AccordionGroup>