> For the complete documentation index, see [llms.txt](https://documentation.immuta.com/2024.3/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.immuta.com/2024.3/data-and-integrations/registering-metadata/schema-monitoring/how-to-guides/run-schema-monitoring.md).

# Run Schema Monitoring and Column Detection Jobs

## Manually Run Schema Monitoring Jobs

### Manually Run Schema Monitoring Job for All Data Sources

**Requirement:** Immuta permission `USER_ADMIN`

You can manually run a schema monitoring job globally using the [<mark style="color:blue;">`/dataSource/detectRemoteChanges`</mark> <mark style="color:blue;">endpoint of the Immuta API</mark>](/2024.3/developer-guides/api-intro/immuta-v1-api/data-sources.md#trigger-schema-monitoring-jobs) with an empty payload.

### Manually Run Schema Monitoring Job as a Data Owner

You can manually run a schema monitoring job for all data sources that you own using the [<mark style="color:blue;">`/dataSource/detectRemoteChanges`</mark> <mark style="color:blue;">endpoint of the Immuta API</mark>](/2024.3/developer-guides/api-intro/immuta-v1-api/data-sources.md#trigger-schema-monitoring-jobs) with a payload containing the hostname for your data sources or their individual IDs.

### Manually Run Schema Monitoring Job as a Data User

You can manually run a schema monitoring job for data sources you are subscribed to using the [<mark style="color:blue;">`/dataSource/detectRemoteChanges`</mark> <mark style="color:blue;">endpoint of the Immuta API</mark>](/2024.3/developer-guides/api-intro/immuta-v1-api/data-sources.md#trigger-schema-monitoring-jobs) with a payload containing the hostname for your data source and the table name or data source ID.

## Manually Run a Column Detection Job

1. Navigate to the data source overview page.
2. Click on the **health check icon**.
3. Scroll to Column Detection, and click **Trigger Detection**.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://documentation.immuta.com/2024.3/data-and-integrations/registering-metadata/schema-monitoring/how-to-guides/run-schema-monitoring.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.