> For the complete documentation index, see [llms.txt](https://developer.celigo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.celigo.com/cli/commands/sync-jobs.md).

# sync-jobs

Inspect and cancel sync jobs — the read-only executions produced by [`syncs run`](/cli/commands/syncs.md). Each sync job tracks extraction, loading, and error counts across a sync's tables. Use this command to list a sync's jobs, fetch one by ID, read its errors, and cancel a job that is still running.

**REST API**: [Syncs](https://developer.celigo.com/api/api-reference/sync-jobs)

```
celigo sync-jobs <subcommand> [args] [flags]
```

Supports all [global flags](/cli/getting-started/global-flags.md).

## Subcommands

| Subcommand           | Purpose                                 |
| -------------------- | --------------------------------------- |
| `list`               | List the jobs for a sync, newest first. |
| `get <syncJobId>`    | Get a sync job by ID.                   |
| `errors <syncJobId>` | List errors for a sync job.             |
| `cancel <syncJobId>` | Cancel a single sync job.               |

***

## `celigo sync-jobs list`

List the jobs for a sync, newest first. Pass the sync with `--sync`, and optionally bound the window with `--created-gte` / `--created-lte`.

**Signature**

```bash
celigo sync-jobs list --sync <syncId> [flags]
```

**Arguments**

None.

**Flags**

| Flag                   | Type   | Default | Description                                                               |
| ---------------------- | ------ | ------- | ------------------------------------------------------------------------- |
| `--sync <syncId>`      | string | —       | Sync whose jobs to list.                                                  |
| `--created-gte <date>` | string | —       | Only jobs created on/after this date (ISO 8601, plain date, or epoch ms). |
| `--created-lte <date>` | string | —       | Only jobs created on/before this date.                                    |

**Example**

```bash
celigo sync-jobs list --sync 5f83a9b2c7d3e8f1a2b3c4d5 --created-gte 2026-06-01 --format table
```

**Corresponds to**: [`GET /v1/syncs/{_syncId}/syncJobs`](https://developer.celigo.com/api/api-reference/sync-jobs) (operationId: `listSyncJobs`)

***

## `celigo sync-jobs get`

Get a single sync job by ID.

**Signature**

```bash
celigo sync-jobs get <syncJobId>
```

**Arguments**

| Argument      | Type   | Required | Description  |
| ------------- | ------ | -------- | ------------ |
| `<syncJobId>` | string | Yes      | Sync job ID. |

**Example**

```bash
celigo sync-jobs get 6a1b2c3d4e5f6a7b8c9d0e1f
```

**Corresponds to**: [`GET /v1/syncJobs/{_syncJobId}`](https://developer.celigo.com/api/api-reference/sync-jobs) (operationId: `getSyncJobById`)

***

## `celigo sync-jobs errors`

List the errors recorded for a sync job.

**Signature**

```bash
celigo sync-jobs errors <syncJobId>
```

**Arguments**

| Argument      | Type   | Required | Description  |
| ------------- | ------ | -------- | ------------ |
| `<syncJobId>` | string | Yes      | Sync job ID. |

**Example**

```bash
celigo sync-jobs errors 6a1b2c3d4e5f6a7b8c9d0e1f --format json
```

**Corresponds to**: [`GET /v1/syncJobs/{_parentJobId}/errors`](https://developer.celigo.com/api/api-reference/sync-jobs) (operationId: `listSyncJobErrors`)

***

## `celigo sync-jobs cancel`

Cancel a single sync job by ID. Prompts for confirmation unless `-y` is passed.

> ⚠️ **Cancelling a sync job cannot be undone.** Extraction and loading stop immediately, which can leave data partially synced. Re-run the sync to finish.

**Signature**

```bash
celigo sync-jobs cancel <syncJobId> [flags]
```

**Arguments**

| Argument      | Type   | Required | Description  |
| ------------- | ------ | -------- | ------------ |
| `<syncJobId>` | string | Yes      | Sync job ID. |

**Flags**

| Flag        | Type    | Default | Description        |
| ----------- | ------- | ------- | ------------------ |
| `-y, --yes` | boolean | `false` | Skip confirmation. |

**Example**

```bash
celigo sync-jobs cancel 6a1b2c3d4e5f6a7b8c9d0e1f -y
```

**Corresponds to**: [`PUT /v1/syncJobs/{_syncJobId}/cancel`](https://developer.celigo.com/api/api-reference/sync-jobs) (operationId: `cancelSyncJob`)

***

## Gotchas

* **Sync jobs are read-only executions.** They are produced by [`syncs run`](/cli/commands/syncs.md), not created directly. `cancel` is the only mutating subcommand here.
* **`list` requires `--sync`.** Jobs are scoped to a sync; pass the sync ID with `--sync` to list its jobs.
* **`cancel` vs `syncs cancel-jobs`.** `sync-jobs cancel <syncJobId>` cancels one job; [`syncs cancel-jobs <syncId>`](/cli/commands/syncs.md) cancels every running job for a sync.
* **Errors are read from the parent job.** The errors endpoint keys off the parent job ID — pass the job ID returned by `list` or `run`.

## Related

* [syncs](/cli/commands/syncs.md) — trigger runs, cancel all jobs for a sync, and discover supported source/destination apps.
* [integrations](/cli/commands/integrations.md) — the container that owns syncs.
* [jobs](/cli/commands/jobs.md) — flow execution history (distinct from sync jobs).


---

# 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://developer.celigo.com/cli/commands/sync-jobs.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.