---
title: "Skip future sessions by count or time"
method: POST
path: "/api/schedules/{id}/skip"
tags: ["Schedule"]
---

# Skip future sessions by count or time

`POST /api/schedules/{id}/skip`

## Path parameters

- `id` integer, required

## Request body

- RestScheduleSkipRequest — Request body for skipping a schedule
  - `count` integer — skip given number of sessions. nextTime or (fromTime and count) are required.
  - `dryRun` boolean, required — dry run
  - `fromTime` string, date-time — skip before the time. nextTime or (fromTime and count) are required.
  - `nextRunTime` string, date-time — next run time
  - `nextTime` string — next time. nextTime or (fromTime and count) are required.

## Response `200`

default response

- RestScheduleSummary — Response of a schedule with summary
  - `createdAt` string, date-time, required — created time
  - `disabledAt` string, date-time — disabled time
  - `id` string, required — schedule ID
  - `nextRunTime` string, date-time, required — next run time
  - `nextScheduleTime` string, required — next schedule time
  - `project` IdAndName, required — Name and ID
    - `id` string, required — ID
    - `name` string, required — name
  - `updatedAt` string, date-time, required — updated time
  - `workflow` IdAndName, required — Name and ID
    - `id` string, required — ID
    - `name` string, required — name

---

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