---
title: "Create jobs schedule"
method: PUT
path: "/{env_id}/{flow_id}/{tenant}/jobs/schedule"
---

# Create jobs schedule

`PUT /{env_id}/{flow_id}/{tenant}/jobs/schedule`

Create a new schedule for a tenant

## Path parameters

- `env_id` string, required
- `flow_id` string, required
- `tenant` string, required

## Request body

- object
  - `schedule_expression` string, required — cron expression defining how often sync should occur e.g. `cron(0 0 * * *)`
  - `job_type` 'read' | 'write' — For v2 flows, defines the type of job. Accepts "read" or "write."
  - `state` 'DISABLED' | 'ENABLED' — Whether this schedule should be DISABLED or ENABLED
  - `connector_id` string — Optional specific connector or tap ID to set the schedule on
  - `override_start_date` string, date-time — Optional override for the `start_date` that jobs will run with. This will ignore state bookmarks and any `start_date` in the config.
  - `override_selected_tables` object — Override the unified schema selection for this schedule
  - `override_field_map` object — Override the field map selection for this schedule
  - `environment_variables` object — Set optional environment variables for the job to use (generally for use in the ETL).
  - `schedule_jitter_minutes` integer, nullable — Jitter window in minutes for default schedules. Only allowed when tenant is `default`; set to null to clear.

## Response `200`

200

- object

## Other responses

- `400` — 400

---

[API](https://skmtc.net/hotglue/apis/hotglue-api.md) · [All operations](https://skmtc.net/hotglue/apis/hotglue-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/hotglue/hotglue-api/revisions/30ff54d01ec0/schema)