run_schedule
Trigger a deployed app's schedule to run now and receive a run ID and outcome, so you can track manual executions and detect skipped overlapping runs.
Instructions
Call a schedule's path now (a manual run); answers 202 at once.
Returns ``{run_id, outcome}``: ``running``, or ``skipped_overlap`` when
the previous run is still out. Read the result with
``list_schedule_runs``. Refusals: 404 ``schedule.not_found``, 409
``schedule.service_not_running`` (stopped, failed, degraded or
mid-cutover), 409 ``schedule.restart_required``.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"name": "<name>",
"schedule_name": "<schedule_name>"
},
"name": "run_schedule"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Name (or row id) of an existing deployed app — only kind 'service' can be exposed: ``share_service``/``add_domain`` refuse a model or database with 422 ``*.kind_unsupported``, while the remove tools just find nothing to undo. | |
| schedule_name | Yes | Schedule name: lowercase letters, digits and '-', 1-32 characters, starting with a letter (e.g. ``morning``); the app receives it as ``X-Nerdit-Schedule``. | |
| idempotency_key | No | Caller-chosen key: a retry with the same key replays the first result instead of acting twice. Omit and a fresh key is minted per call, so each call acts. |