---
title: "Reschedule DAG-run with a new run ID"
method: POST
path: "/dag-runs/{name}/{dagRunId}/reschedule"
tags: ["dag-runs"]
---

# Reschedule DAG-run with a new run ID

`POST /dag-runs/{name}/{dagRunId}/reschedule`

Launch a fresh DAG-run from a historic execution while reusing its stored parameters.

## Path parameters

- `name` string, regex, required — Name of the DAG
- `dagRunId` string, required — Unique identifier for the DAG-run. The special value 'latest' can be used to reference the most recent DAG-run.

## Query parameters

- `remoteNode` string

## Request body

- object
  - `dagRunId` string — Explicit run ID for the new DAG-run; if omitted a new ID is generated.
  - `dagName` string — Optional DAG name override for the new run.
  - `useCurrentDagFile` boolean — When true, reschedule from the current contents of the original DAG file instead of the stored historical YAML snapshot.

## Response `200`

Successfully scheduled a new DAG-run

- object
  - `dagRunId` string, required — Unique identifier for the DAG-run. The special value 'latest' can be used to reference the most recent DAG-run.
  - `queued` boolean, required — Indicates whether the run was queued instead of starting immediately.

## Other responses

- `400` — Invalid request parameters
- `404` — Historic run not found
- `409` — Conflict (run ID already exists)
- `default` — Generic error response

---

[API](https://skmtc.net/dagucloud/apis/dagu.md) · [All operations](https://skmtc.net/dagucloud/apis/dagu/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/dagucloud/dagu/revisions/4a98622e8b7e/schema)