---
title: "Retrigger a job"
method: POST
path: "/{env_id}/{flow}/{tenant_id}/jobs/retrigger"
tags: ["Jobs"]
---

# Retrigger a job

`POST /{env_id}/{flow}/{tenant_id}/jobs/retrigger`

Retriggers a job based on the provided job_root and parameters. Returns the job details for the retriggered job.

## Path parameters

- `env_id` string, required
- `flow` string, required
- `tenant_id` string, required

## Request body

- object
  - `job_root` string, required — The job root (aka s3_root) to retrigger
  - `skip_sync` boolean — Whether to skip or rerun the sync step. If true, the ETL script will use the job's existing synced data.
  - `skip_etl` boolean — Whether to skip or rerun the ETL step. If true, the export step will use the job's existing ETL data.
  - `skip_webhooks` boolean — Whether to send job status webhooks for the retriggered job.

## Response `200`

Job successfully retriggered

- object — The details for the retriggered job.
  - `job_id` string — The ID of the retriggered job
  - `env_id` string — The ID of the environment
  - `flow_id` string — The ID of the flow
  - `job_name` string — The name of the retriggered job
  - `tenant` string — The ID of the tenant
  - `s3_root` string — The S3 root of the retriggered job

## Other responses

- `400` — Invalid request (missing job or flow, job still running, etc.)

---

[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/ec83efeae3d5/schema)