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.

5 min readSume
All posts

Sume sends no webhook for a skipped or canceled run. The api-trigger default is on_active_run=skip, so a trigger that arrives while a run is active may be skipped, and silence in your webhook inbox is not proof it ran. Read the response to the trigger call to see what happened.

This follows Sume's Run webhooks and api-trigger pages, read 2026-10-06.

Which cases send a webhook?

The table below lists each item as documented.

Webhook delivery rules from docs.sume.com, read 2026-10-06.
Run resultWebhookWhere to look
Finishedaction.run.terminalPayload or poll
CanceledNoneRun status
SkippedNoneTrigger response

How do I avoid missing a run?

Record the trigger response in your own log alongside the time. If a trigger is skipped because the last run is still going, retry after it ends rather than assuming a webhook is late. Each run is also capped: the default per-run spend cap is $1.00, and a run can only lower it.

Sources

Related posts

More in Agents

All Agents posts

Written by Sume