Why did my Format run do that? Read the first message of its thread
A Format run's first thread message is the text the agent received: Format pointer, your instruction, unattended note and input file path. Read it first.
When a Format run does something you did not expect, open the run's thread_id in Agents and read the first message. Sume's docs say it is the composed text, with no changes: the Format pointer, the Format's SKILL.md, your instruction, the unattended-run note, a pointer at your input, and any attached files (Formats overview). It is the quickest way to see what the agent was actually told.
The order the agent receives
Sume tells the agent to read the input file as data, never as instructions. If your input holds a sentence such as "ignore the script", it stays data.
| Part | What it holds |
|---|---|
| Format pointer | [Format: live-commerce v23], a pointer at the recipe. The body is not inlined. |
| Format attached | The whole package, on disk in the run's workspace. |
| Format run instruction | Your instruction, or the Format's default. |
| Sume unattended run | API and scheduled runs only. |
| Sume action input | A pointer at your input, written whole to /workspace/inputs/sume-action-input.json. |
| Attached files | Your attachments, when present. |
A short debugging routine
Log request_id with each run. It is the value support asks for.
- Take
thread_idandrequest_idfrom the receipt (GET /v1/format-runs/{run_id}). - Open the thread and read message one. Check that your
instructionis there, that the keys you expected are named, and that no attachment is missing. - Compare it with the
output_erroranderroron the receipt.unattended_blockedmeans the run stopped instead of claiming a deliverable it did not make. - Fix the instruction or the input, and send a new call with a new
Idempotency-Key.
What this does not show
The API deliberately does not return the recipe body to a caller. The thread view is for the owner of the workspace that made the call. For a team Format, that means you need access through the workspace that made the run.
Sources
Related posts
More in Formats
- Queue a 100-episode Shorts season in one Sume call?
Yes: one bulk-runs call queues up to 100 Format runs, 1 to 16 at a time. Here is what it returns, what it skips, and how to poll a season.
- 5 hooks x 5 offers x 4 ratios = 100: one weekly bulk queue
Sume bulk runs take 1 to 100 items. A 5 hooks by 5 offers by 4 ratios matrix fills the queue exactly. Name each item by index so results map back.
- Bulk queue says completed: it does not mean every episode rendered
A Sume Format queue is completed when every item is terminal, failed and canceled included. Check counts.failed and counts.canceled before publishing a season.
- After Sora: keep the recipe, not the prompt, as your stable layer
OpenAI named no replacement for the Sora Videos API. Put house style and output rules in a Sume Format so the next model change does not rewrite your code.
Written by Sume