Why the Sume API hides a schedule's instructions text
GET /v1/actions returns the cron, model, cap and schema of a Sume schedule but not its instructions text. Read and edit instructions in the dashboard.
You list schedules with GET /v1/actions and expect the prompt back. It is not there. The Scheduled page states that the public shape does not include the instructions text, calls that intentional, and says to use the dashboard to read and edit instructions.
What the API does return
- Identity and state:
id(aut_...),object: "action",title,status. - Trigger:
trigger_type,api_trigger_enabled,cronwithexpr,timezone,next_run_at. - Behavior:
model,output_schema,primary_output_key,generation_spend_cap_usd_micros. - Timing and entry point:
last_run_at,created_at,updated_at,invoke_url.
What that means for your process
Instructions persist across runs and are the prompt; data from the caller arrives separately as input, as in Advanced: run a schedule via API. So keep a copy of the instructions in your own repo if you need review history, and treat the dashboard as the place they are applied. A prompt change is made there, and the API cannot create, edit or delete a schedule either.
Empty instructions cannot run; a run request against such a schedule fails with 400. If a run behaves oddly, compare the dashboard text with your copy before you blame the model, then check the receipt's output_error and error fields.
Passing per-run variation
Put what changes in input, up to 64 properties and 2 MiB, and keep what stays the same in the saved instructions. That split is also why a cron-only schedule needs no payload, and why the Create a schedule page describes instructions as the prompt that the Agent executes on each run.
Sources
Related posts
More in Agents
- Agent Completion 400: generation_spend_cap_usd has no default
Your POST to /v1/agent/completions returns 400? generation_spend_cap_usd is required and has no default. Add it, and pick a number from a real run.
- assets_download_url MCP tool: a short-lived link for an uploaded asset
The hosted MCP tool assets_download_url returns a short-lived signed URL for a first-party asset. Use it only when asked, and never echo the URL in a report.
- Captions drift after cutting pauses: burn them on the final render
Cut pauses first, then caption. Word times from the original clip no longer match once silence is gone. Run Sume video-captions on the trimmed render.
- Create a Sume schedule by API? Dashboard first, then trigger by API
The Sume API cannot create or edit schedules. Create it in the dashboard with a cron or an api trigger, then call it from code. What each trigger type means.
Written by Sume