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

# Jobs

> Create and operate sync Jobs under Data — tables, runs, transforms, schema evolution, and validation.

Jobs move data between connections. A Job selects a source and destination, tables to sync, optional transforms, sync mode, schedule, and execution mode (**Hosted** or **Agent**). Each execution is a **run** with progress, events, and history.

<Note>
  Match **projects** under **Match → Projects** are not sync Jobs. Use Jobs to move data; use Match to resolve duplicate entities.
</Note>

In the sidebar, Jobs sit under the **Data** group (with **Connections** and **Files**), not under Know / Trust / Match.

***

## Open Jobs

1. Select **Data → Jobs**.

Page title: **Jobs**. Primary action: **New Job**.

Search placeholder: **Search jobs…**. Status chips filter the list. Empty state: **No sync jobs yet** (*A job connects a source to a destination and keeps your data in sync on a schedule.*) with **+ New Job**.

***

## Create a Job

1. **Data → Jobs → New Job** (page title **New job**).
2. Complete the wizard steps in order:

| Step | Label |
| - | - |
| 1 | **Source** |
| 2 | **Destination** |
| 3 | **Tables** |
| 4 | **Field Mapping** |
| 5 | **Configure** |

3. On **Configure**, set sync mode, destination write mode, schedule, retries / workers, and execution mode as needed.
4. Under advanced options, **Job Type** is **ETL** or **Reverse ETL**.
5. Click **Create Job**.

Typical sequence after create: open the Job → **Rerun** (or wait for schedule) → inspect **Runs** / **View Logs**.

See [ETL pipelines](/pipelines/etl) and [Reverse ETL](/pipelines/reverse-etl) for mode detail.

***

## Job detail

Open a Job from the list. Tabs:

| Tab | Purpose |
| - | - |
| **Overview** | Pipeline summary, progress, errors, Trust status, performance history, **Notes** |
| **Tables** | Per-table status; search and status chips; **+ Add Table**; **Rerun N** / **Remove N** |
| **Runs** | Execution history; **View Logs** opens **Events & Logs** |
| **Schema Evolution** | Pending proposals when the source schema changes |
| **Transforms** | Column mappings, filters, computed columns (**Configure Transforms** when empty) |
| **Data Quality** | Pipeline validation report and semantic rules (**Run Validation**) |

### Tables

* Filter by status with the chip group.
* Search table names.
* **+ Add Table** opens **Add Tables**.
* Selection actions: **Rerun N**, **Remove N**.

### Runs

1. Review run history.
2. Click **View Logs** for **Events & Logs** (`/jobs/{id}/events`).
3. If there are no runs: **No runs yet** — *Rerun this job to create the first execution.* → **Rerun job**.

### Common actions

| Action | Label / dialog |
| - | - |
| Restart full job | **Rerun** → confirm **Rerun Job** |
| Stop a running job | **Cancel** → **Cancel Job** |
| Retry failures | Overflow **Retry Failed Tables** |
| Hosted pause / resume | **Pause** / **Resume** when available |
| Scratch restart while active | **Restart from scratch** |

***

## Jobs vs Match projects

| | **Jobs** | **Match projects** |
| - | - | - |
| Goal | Move / sync data | Resolve duplicate entities |
| Nav | **Data → Jobs** | **Match → Projects** |
| Output | Destination tables filled | Groups → goldens → optional write-back |

***

## Related articles

* [ETL](/pipelines/etl)
* [Reverse ETL](/pipelines/reverse-etl)
* [Monitoring](/pipelines/monitoring)
* [Events](/pipelines/events)
* [Validation](/pipelines/validation)
* [Schema evolution](/concepts/schema-evolution)
* [Transforms](/concepts/transforms)
* [Match overview](/match/overview)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.