runSchedule

Run a schedule now

Start one run of a schedule now, outside its times, to test it. A run takes minutes and spends AI credit, so ask the person first. This returns at once; call listSchedules after a few minutes for lastStatus and lastError.

Arguments

Argument	Type	Required	Description
`name`	string	required	The schedule name: lowercase letters, digits and hyphens, for example coaching-posts-mon-6pm.

Scopes

schedules:manage

Annotations

Read only: no
Destructive: no

When to use

Call runSchedule to test a schedule without waiting for its next time. A run takes minutes and spends AI credit, so ask the person first.

The schedule tools need the schedules:manage scope. Only admin and staff can hold it. Schedules belong to the whole organisation: every admin and staff user sees and changes the same list, which also shows in the Sasha web interface, in Menu → Tasks.

name (required) picks the schedule. The run uses the schedule's skill and time limit, and it runs even when the schedule is paused. The tool returns as soon as the run starts. Call listSchedules after a few minutes: lastStatus and lastError show how it ended.

Example

{ "name": "client-digest-thu-6pm" }

The structured result (structuredContent):

{
  "started": "client-digest-thu-6pm",
  "skill": "weekly-client-digest"
}

Refusals and what to do

A schedule tool refuses with an error result. Its text is Error in runSchedule: <code>: <reason>.

schedule_not_found: no schedule has this name. Call listSchedules.
agent_skill: the schedule's skill is a report agent. Start a report from its app, with Run now.
If the connection does not hold schedules:manage, the tool is not in your tool list, and a call to it returns MCP error -32602: Tool runSchedule not found. Only admin and staff can hold the scope, so a member's connection never has the schedule tools. A connection approved before the scope existed must reconnect, or the person mints a new token. Read the permissions section of getDocs.
Arguments that do not match the schema are refused before the tool runs, for example a name with capital letters or spaces, or an extra argument.
internal:unexpected (request <id>): something failed inside Sasha. Quote the request id in suggestImprovement.

listSchedules lists the schedules and their last result.
createSchedule adds a schedule.
updateSchedule changes, pauses or restarts a schedule.
deleteSchedule removes a schedule.
runSchedule runs a schedule once now.
getDocs has a schedules section with the same rules.