Run schedule
run_scheduleRun one of a project's schedules now, to test its route, and wait for the answer: status ok (the route answered 2xx) or failed, with http_status, what the app answered (response), and error_explained in plain words. It wakes the app first if it sleeps. A test run is never retried and does not count toward the failure email. While a run of that schedule is going, it reports that run instead of starting another. A 401 means the route's signature check does not match: it must compute HMAC-SHA256 over t + "." + the raw body with SPAWNPOINT_RUN_SECRET. A 404 means the app has no such route.
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": {
"project_id": "<project_id>",
"name": "<name>"
},
"name": "run_schedule"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | the schedule's name (its path when it was set without one) | |
| project_id | Yes | the id of the project |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| note | No | ||
| woke | Yes | ||
| run_id | Yes | ||
| status | Yes | ||
| response | No | ||
| duration_ms | No | ||
| http_status | No | ||
| error_explained | No |