> ## Documentation Index
> Fetch the complete documentation index at: https://docs.plungeai.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Resume a schedule

> Resume a paused schedule.


## OpenAPI

```yaml openapi.json post /v1/schedules/{id}/resume
openapi: 3.1.0
info:
  title: Ocean One API
  version: 2.3.0
servers:
  - url: https://api.plungeai.com
paths:
  /v1/schedules/{id}/resume:
    post:
      operationId: post-v1-schedules-id-resume
      tags:
        - Schedules
      security:
        - ozkBearer: []
      parameters:
        - name: id
          in: path
          required: true
          schema:
            type: string
          description: Schedule id (job_…)
      summary: Resume a paused schedule
      responses:
        "200":
          description: The active schedule Response format negotiates via the `format` field, an Accept header (application/json, text/yaml, text/markdown, text/plain), or the request Content-Type mirror; default JSON.
          content:
            application/json:
              schema:
                type: object
                properties:
                  schedule:
                    type: object
                    properties:
                      id:
                        type: string
                      name:
                        type: string
                      description:
                        type:
                          - string
                          - "null"
                      job_type:
                        type: string
                        enum:
                          - workflow
                          - heartbeat
                          - agent
                          - query
                      schedule:
                        type: string
                        description: Cron expression, or @once for a one-time schedule
                      timezone:
                        type:
                          - string
                          - "null"
                        description: IANA zone the cron is read in; null = UTC
                      status:
                        type: string
                        enum:
                          - active
                          - paused
                      workflow_id:
                        type:
                          - string
                          - "null"
                      target:
                        type: string
                        description: The workflow id, or a heartbeat’s JSON spec
                      parameters:
                        type:
                          - object
                          - "null"
                        description: deliver targets, input, … as stored
                      next_run_at:
                        type:
                          - integer
                          - "null"
                        description: ms epoch
                      last_run_at:
                        type:
                          - integer
                          - "null"
                        description: ms epoch
                      ends_at:
                        type:
                          - integer
                          - "null"
                        description: ms epoch after which a due schedule is removed instead of run
                      created_at:
                        type: integer
                      updated_at:
                        type: integer
            text/yaml:
              schema:
                type: string
            text/markdown:
              schema:
                type: string
            text/plain:
              schema:
                type: string
        "401":
          description: unauthorized — missing, invalid or revoked ozk_ key
          content:
            application/json:
              schema:
                $ref: "#/components/schemas/Error"
        "404":
          description: "schedule_not_found — no schedule with that id for this key (a foreign, missing or deleted id answers alike); not_found — no route for this method on this path: every other method answers it"
          content:
            application/json:
              schema:
                $ref: "#/components/schemas/Error"
        "502":
          description: scheduler_error — the scheduler failed or did not answer; no detail is returned, retry
          content:
            application/json:
              schema:
                $ref: "#/components/schemas/Error"
components:
  schemas:
    Error:
      type: object
      description: Standard error envelope. Every error response also carries an `X-Error-Code` response header equal to error.code, so a client branches on the header regardless of the negotiated body format (json | yaml | markdown | text). When the request created an execution, the `X-Execution-Id` response header is also set. Errors follow the negotiated format like success bodies.
      properties:
        error:
          type: object
          properties:
            code:
              type: string
            message:
              type: string
            connect:
              type: object
              description: "On a 424 connection_required / credential_required: where the missing connection is made."
              properties:
                provider:
                  type: string
                method:
                  type: string
                  enum:
                    - oauth
                    - api_key
                    - wallet
                link:
                  type: string
                  example: POST /v1/connections/stripe/link
          required:
            - code
            - message
          additionalProperties: true
      required:
        - error
  securitySchemes:
    ozkBearer:
      type: http
      scheme: bearer
      description: "ozk_ platform API key (Authorization: Bearer ozk_…)"
```