> For the complete documentation index, see [llms.txt](https://upsolver.gitbook.io/content/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://upsolver.gitbook.io/content/reference-1/sql-commands/jobs/create-job/transformation/job-options.md).

# Job Options

The following job options can be applied to all targets. See the links below for [target-specific job options](#target-specific-job-options).

```sql
[ COMMENT = '<comment>' ]
[ COMPUTE_CLUSTER = <cluster_identifier> ]
[ END_AT = { NOW | timestamp } ]
[ RUN_INTERVAL = <integer> { MINUTE[S] | HOUR[S] | DAY[S] } ]
[ RUN_PARALLELISM = <integer> ]
[ START_FROM = { NOW | BEGINNING | timestamp } ]
```

#### Jump to

* [`COMMENT` ](#comment-editable)
* [`COMPUTE_CLUSTER`](#compute_cluster-editable)&#x20;
* [`END_AT`](#end_at-editable)
* [`RUN_INTERVAL`](#run_interval)
* [`RUN_PARALLELISM`](#run_parallelism-editable)
* [`START_FROM`](#start_from)

#### `COMMENT` — editable

Type: `text`

(Optional) A description or comment regarding this job.

#### `COMPUTE_CLUSTER` — editable

Type: `identifier`

Default: The sole cluster in your environment

(Optional) The compute cluster to run this job.

This option can only be omitted when there is just one cluster in your environment.

Once you have more than one compute cluster, you are required to provide which one to use through this option.

#### `END_AT` — editable

Values: `{ NOW | timestamp }`

Default: Never

(Optional) Configures the time to stop inserting data. Data after the specified time is ignored.

If set as a `timestamp`, it should be aligned to the [`RUN_INTERVAL`](#run_interval).

For example, if [`RUN_INTERVAL`](#run_interval) is set to 5 minutes, then you can set an end time of 12:05 PM but not 12:03 PM. Additionally, the timestamp should be based in UTC and in the following format: `TIMESTAMP 'YYYY-MM-DD HH:MM:SS'`.

If set to `NOW`, the job runs up until the previous full period. For example, if the current time is 12:03 PM, creating the job with a [`RUN_INTERVAL`](#run_interval) of 5 minutes ending at `NOW` means that the last task executed by the job ends at 12:00 PM.

#### `RUN_INTERVAL`

Value: `<integer> { MINUTE[S] | HOUR[S] | DAY[S] }`

Default: `1 MINUTE`

(Optional) How often the job runs.

The runs take place over a set period of time defined by this interval and they must be divisible by the number of hours in a day.

For example, you can set `RUN_INTERVAL` to 2 hours (the job runs 12 times per day), but trying to set `RUN_INTERVAL` to 5 hours would fail since 24 hours is not evenly divisible by 5.

#### `RUN_PARALLELISM` — editable

Type: `integer`

Default: `1`

(Optional) Controls how many jobs run in parallel to process a single minute of data from the source table.&#x20;

Increasing this can lower the end-to-end latency if you have lots of data per minute.

#### `START_FROM`

Values: `{ NOW | BEGINNING | timestamp }`

Default: `BEGINNING`

(Optional) Configures the time to start inserting data from. Data before the specified time is ignored.

If set as a `timestamp`, it should be aligned to the [`RUN_INTERVAL`](#run_interval).&#x20;

For example, if [`RUN_INTERVAL`](#run_interval) is set to 5 minutes, then you can set a start time of 12:05 PM but not 12:03 PM. Additionally, the timestamp should be based in UTC and in the following format: `TIMESTAMP 'YYYY-MM-DD HH:MM:SS'`.

If set to `NOW` or `BEGINNING`, the job runs from the previous full period. For example, if the current time is 12:03 PM, creating the job with a [`RUN_INTERVAL`](#run_interval) of 5 minutes starting from `NOW` means that the first task executed by the job starts from 12:00 PM.

***

## Target-specific job options

Visit the pages below for target-specific job options:

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-cover data-type="files"></th></tr></thead><tbody><tr><td><a href="/pages/YxsnatbITYKLo6xyLejX">View Job Options</a></td><td><a href="/files/ZgtvfQEpJJJPQ77AsRfF">/files/ZgtvfQEpJJJPQ77AsRfF</a></td></tr><tr><td><a href="/pages/WMhAXnGlAoluCnkhr3Mc">View Job Options</a></td><td><a href="/files/CXDYOoq6wmytr479i22o">/files/CXDYOoq6wmytr479i22o</a></td></tr><tr><td><a href="/pages/c8LdMf4jwBdPmLh3EZoe">View Job Options</a></td><td><a href="/files/eovVWDhzuF4uhJodD5mV">/files/eovVWDhzuF4uhJodD5mV</a></td></tr><tr><td><a href="/pages/b6bD5oKYDKSrTRzWIPVA">View Job Options</a></td><td><a href="/files/bhFIblO698hgb0n6rl5I">/files/bhFIblO698hgb0n6rl5I</a></td></tr><tr><td><a href="/pages/vAX8pxoAT2bIRpzG0oro">View Job Options</a></td><td><a href="/files/coGVVvaE5ryRQWfttS84">/files/coGVVvaE5ryRQWfttS84</a></td></tr><tr><td><a href="/pages/1EUJyWRekPa8cv4yToKQ">View Job Options</a></td><td><a href="/files/6Za7iqPqKyuYLLuu2hrk">/files/6Za7iqPqKyuYLLuu2hrk</a></td></tr><tr><td><a href="/pages/khKWZi0pXWGqFowgWKn7">View Job Options</a></td><td><a href="/files/jvrsGGky0IKXTbzaqA2c">/files/jvrsGGky0IKXTbzaqA2c</a></td></tr><tr><td><a href="/pages/13uTYAyFzvQzBGQM1Fhp">View Job Options</a></td><td><a href="/files/REealkIM1dwB4fy154K2">/files/REealkIM1dwB4fy154K2</a></td></tr><tr><td><a href="/pages/pLZtMbTCiQdpKFN3Xgg1">View Job Options</a></td><td><a href="/files/wkiXKQeWXfiQT4lqGTtp">/files/wkiXKQeWXfiQT4lqGTtp</a></td></tr></tbody></table>


---

# 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://upsolver.gitbook.io/content/reference-1/sql-commands/jobs/create-job/transformation/job-options.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.