Sume Action overlap: on_active_run skip gives 200, reject gives 409

What happens when a Sume Action run starts while the last one is active: skip gives 200 with status skipped, reject gives 409 action_run_in_progress.

5 min readSume
All posts

on_active_run decides what a new start does when a run of the same Action is still active. With skip, the call returns 200 with status skipped and skip_reason: previous_run_active; no work starts and nothing is billed. With reject, it returns 409 action_run_in_progress. The Action default is skip, while a Format defaults to allow, so a copied Format snippet behaves differently on an Action.

Treat skipped as a terminal outcome, not a failure. A cron job that overlaps itself should skip; an operator who wants to know about the collision should reject.

Policy outcomes

on_active_run policies per Sume docs (read 2026-10-03)
PolicyResponse when previous run activeDefault for
skip200, status skippedAction
reject409 action_run_in_progressNeither
allowNew run startsFormat

In code

Branch on status before you read results: a skipped receipt carries no output. If you need the earlier run, read it by id rather than starting another.

Sources

Related posts

More in Agents

All Agents posts

Written by Sume