Why Sume's scheduled-run API does not return instructions text
The public scheduled-run shape omits the instructions text. Read and edit it in the dashboard; schedules have no MCP tool or write endpoint.
Sume's public scheduled-run shape does not include the instructions text. To read or change what a schedule tells the agent, use the dashboard. There is no MCP tool, CLI command or write endpoint for schedules, so a script cannot rewrite instructions either.
This comes from Sume's Scheduled, Runs and results and api-trigger pages, read 2026-10-06.
What can the API do?
The table below lists each item as documented.
| Task | Where | Note |
|---|---|---|
| Read instructions text | Dashboard only | Not in the public shape |
| Edit instructions | Dashboard only | No write endpoint |
| Trigger a run | /v1/actions API trigger | Ids start with aut_ |
| List runs | Scheduled runs endpoints | Schedules are not in /v1/jobs |
What does that mean for audits?
If you log API responses for review, the instructions are not in them. Record who edited a schedule in the dashboard and keep the text in your own change notes. The run itself reports results; events_url is always null, so there is no event stream to subscribe to.
What stays in your control?
Each schedule has a per-run spend cap. The default is $1.00; a run can only lower it, because the cap is clamped to the smaller value. null means no automation ceiling, and 0 is rejected. The api-trigger default for an active run is on_active_run=skip.
Sources
More in Agents
- Sume scheduled run returned skipped: detect previous_run_active
A Sume scheduled run that overlaps another returns 200 with status skipped, not an error. Check skip_reason in code, and choose reject if a drop must be loud.
- Scheduled Sume run missing from /v1/jobs: it is not a job
A schedule run is not a generation job, so it never appears in /v1/jobs and jobs_wait cannot wait on it. Read it from /v1/action-runs/{run_id} instead.
- Skipped Sume scheduled run: no webhook, read the create response
A skipped or canceled Sume run sends no webhook. For api-trigger, on_active_run=skip is the default, so check the create response, not just your webhook inbox.
- Did my Sume cron schedule fire? Read last_run_at and next_run_at
GET /v1/actions/{id} returns last_run_at and cron.next_run_at. Compare them with the run list to see if a schedule fired, without opening the dashboard.
Written by Sume