get-schedule

Read one schedule by its schedule_id. Returns the agent or process flow it runs, its goal, its cron expression or single instant, its status, how many times it has run and last_execution_id — which get-execution takes unchanged. A schedule in another project reports not found.

What it is called on each surface

The wire name is get-schedule everywhere: it is what the Wexa MCP server advertises, the REST path is POST /v1/get-schedule, and each SDK exposes it under its own language's naming convention.

Surface	Name
Wexa MCP server	`get-schedule`
REST API	`POST /v1/get-schedule`
TypeScript SDK	`fabric.getSchedule()`
Python SDK	`fabric.get_schedule()`

Arguments

1 of the 1 argument is required. Omitting a required one is refused before the tool runs, at the validation stage, so it costs nothing and changes nothing.

Argument	Type	Required	Notes
`schedule_id`	string	Required	Schedule id from list-schedules or create-schedule.

project_id, projectID, organization_id and executed_by are not arguments you pass: the platform binds all four from the credential you authenticated with, and both SDKs refuse them before the request leaves your process — see server-bound arguments.

What it returns

The three surfaces wrap this differently, and code written against one will not read another correctly — see return shape.

A real response, captured from a live call to get-schedule:

{
  "content": [
    {
      "type": "text",
      "text": "{\"lifecycle_id\":\"qlc_000188\",\"result\":{\"agentflow_id\":\"6ab1945e7566f41b5c28e303\",\"conclusion\":null,\"created_at\":1790022759.401271,\"created_by\":\"6a79a770b6c128ccc24bfca7\",\"end_at\":null,\"frequency\":\"0 9 * * 1\",\"goal\":\"Summarise yesterday's orders.\",\"last_execution_id\":null,\"limit\":null,\"run_at\":null,\"run_count\":0,\"schedule_id\":\"6ab194677566f41b5c28e30f\",\"status\":\"active\",\"time_zone\":\"Asia/Kolkata\",\"type\":\"recurring\",\"updated_at\":null}}"
    }
  ],
  "isError": false
}

{
  "lifecycle_id": "qlc_000188",
  "result": {
    "agentflow_id": "6ab1945e7566f41b5c28e303",
    "conclusion": null,
    "created_at": 1790022759.401271,
    "created_by": "6a79a770b6c128ccc24bfca7",
    "end_at": null,
    "frequency": "0 9 * * 1",
    "goal": "Summarise yesterday's orders.",
    "last_execution_id": null,
    "limit": null,
    "run_at": null,
    "run_count": 0,
    "schedule_id": "6ab194677566f41b5c28e30f",
    "status": "active",
    "time_zone": "Asia/Kolkata",
    "type": "recurring",
    "updated_at": null
  }
}

// the object you get back IS the result — there is no `.result` to read
{
  agentflow_id: '6ab1945e7566f41b5c28e303',
  conclusion: null,
  created_at: 1790022759.401271,
  created_by: '6a79a770b6c128ccc24bfca7',
  end_at: null,
  frequency: '0 9 * * 1',
  goal: 'Summarise yesterday\'s orders.',
  last_execution_id: null,
  limit: null,
  run_at: null,
  run_count: 0,
  schedule_id: '6ab194677566f41b5c28e30f',
  status: 'active',
  time_zone: 'Asia/Kolkata',
  type: 'recurring',
  updated_at: null
}

// The TS SDK names these camelCase — lifecycleId, traceId — where Python uses
// lifecycle_id and trace_id. Both are non-enumerable: readable, but omitted by
// Object.keys() and JSON.stringify(). `result.lifecycleId` here is undefined.
result.lifecycleId // 'qlc_000188'

# a dict subclass; `result` is already unwrapped
{
 "agentflow_id": "6ab1945e7566f41b5c28e303",
 "conclusion": None,
 "created_at": 1790022759.401271,
 "created_by": "6a79a770b6c128ccc24bfca7",
 "end_at": None,
 "frequency": "0 9 * * 1",
 "goal": "Summarise yesterday's orders.",
 "last_execution_id": None,
 "limit": None,
 "run_at": None,
 "run_count": 0,
 "schedule_id": "6ab194677566f41b5c28e30f",
 "status": "active",
 "time_zone": "Asia/Kolkata",
 "type": "recurring",
 "updated_at": None
}

out.lifecycle_id  # 'qlc_000188' — an attribute, not a key

Keeping the lifecycle_id is what lets you ask later why a call was allowed, refused or held.

Calling it

The same call on all four surfaces. Pick a tab once and every code block in the documentation follows it.

The ids in this example are real: they resolve against the project the documentation is written against, so the call runs as written once you point it at your own deployment. Swap them for the ids of your own objects.

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get-schedule",
    "arguments": {
      "schedule_id": "6ab194677566f41b5c28e30f"
    }
  }
}

curl -sS https://fabric.wexa.ai/v1/get-schedule \
  -H "authorization: Bearer $FABRIC_API_KEY" \
  -H "content-type: application/json" \
  -d '{"schedule_id":"6ab194677566f41b5c28e30f"}'

import { Fabric } from '@wexa-fabric/sdk'

const fabric = new Fabric()
const { result } = await fabric.getSchedule({
  schedule_id: "6ab194677566f41b5c28e30f"
})

from wexa import Fabric

fabric = Fabric()
out = fabric.get_schedule(schedule_id="6ab194677566f41b5c28e30f")

Errors

Both SDKs raise the same typed errors, chosen from the gateway's own error string first and its HTTP status second. get-schedule checks the fabric:orchestrate.read grant, and reaches the seven classes every tool reaches — listed under the common set. These are the ones specific to it:

Error	Status	Raised when
`NotFound`	404	`schedule_id` matches no schedule in this project.
`ConfigurationError`	5xx	`get-schedule` is not available to you. Retrying will not help.

Governance

Every call to get-schedule runs through the same ten-stage lifecycle as every other Wexa tool: the credential is resolved to a scope, the fabric:orchestrate.read grant is checked, quota is drawn down, the arguments are validated, policy rules are evaluated, the call is executed, the result is shaped and redacted, and an audit record is written. The lifecycle_id in the response is the handle to that record.

get-schedule only reads, so it is not marked consequential: it is audited lightly and is never held for approval. It still consumes quota and is still refused by policy like anything else.