---
title: Task configuration options
description: Task options define specific information about a task such as its name, the schedule on which it runs, execution delays, and others.
url: https://docs.influxdata.com/influxdb/cloud/process-data/task-options/
estimated_tokens: 1851
product: InfluxDB Cloud (TSM)
version: cloud
---

# Task configuration options

Task options define specific information about a task. They are set in a Flux script , in the InfluxDB API, or in the InfluxDB user interface (UI). The following task options are available:

-   [name](#name)
-   [every](#every)
-   [cron](#cron)
-   [offset](#offset)

`every` and `cron` are mutually exclusive, but at least one is required.

## name

The name of the task. ***Required***.

***Data type:** String*

In Flux:

```js
option task = {
    name: "taskName",
    // ...
}
```

In a `/api/v2/tasks` request body with `scriptID`:

```json
{
  "scriptID": "SCRIPT_ID",
  "name": "TASK_NAME"
}
```

Replace `SCRIPT_ID` with the ID of your InfluxDB invokable script.

## every

The interval at which the task runs. This option also determines when the task first starts to run, depending on the specified time (in [duration literal](/flux/v0/spec/lexical-elements/#duration-literals)).

***Data type:** Duration*

For example, if you save or schedule a task at 2:30 and run the task every hour (`1h`):

`option task = {name: "aggregation", every: 1h}`

The task first executes at 3:00pm, and subsequently every hour after that.

In Flux:

```js
option task = {
    // ...
    every: 1h,
}
```

In a `/api/v2/tasks` request body with `scriptID`:

```json
{
  "scriptID": "SCRIPT_ID",
  "every": "1h"
}
```

In the InfluxDB UI, use the **Interval** field to set this option.

## cron

The [cron expression](https://en.wikipedia.org/wiki/Cron#Overview) that defines the schedule on which the task runs. Cron scheduling is based on system time.

***Data type:** String*

In Flux:

```js
option task = {
    // ...
    cron: "0 * * * *",
}
```

In a `/api/v2/tasks` request body with `scriptID`:

```json
{
  "scriptID": "SCRIPT_ID",
  "cron": "0 * * * *"
}
```

## offset

Delays the execution of the task but preserves the original time range. For example, if a task is to run on the hour, a `10m` offset will delay it to 10 minutes after the hour, but all time ranges defined in the task are relative to the specified execution time. A common use case is offsetting execution to account for data that may arrive late.

***Data type:** Duration*

In Flux:

```js
option task = {
    // ...
    offset: 10m,
}
```

In a `/api/v2/tasks` request body with `scriptID`:

```json
{
  "scriptID": "SCRIPT_ID",
  "offset": "10m"
}
```

[tasks](/influxdb/cloud/tags/tasks/) [flux](/influxdb/cloud/tags/flux/)