Why did my Format run do that? Read the first message of its thread

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.

A short debugging routine

Log request_id with each run. It is the value support asks for.

• Take thread_id and request_id from the receipt (GET /v1/format-runs/{run_id}).
• Open the thread and read message one. Check that your instruction is there, that the keys you expected are named, and that no attachment is missing.
• Compare it with the output_error and error on the receipt. unattended_blocked means 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.