Sume schedule cap null or 0: what a per-run override can do

A scheduled agent run spends money while nobody is watching, so the cap rules matter more than the cron expression. Sume's docs give four rules for the per-run cap.

What null does and does not mean

null removes the schedule's own ceiling for that run. It does not remove the rest: the docs say wallet balance, generation admission and org limits still apply. So null is not unlimited spend, but it is a larger blast radius than your saved cap, and an unattended caller should have a reason to use it.

A safe pattern

Set the schedule cap to the most one run should ever cost, in the dashboard. Let callers send a smaller generation_spend_cap_usd for cheap runs. Treat null as a code-review item: grep your repo for it. Remember the cap bounds generation, not the agent's own LLM turn, which the Runs and results page says bills a separate wallet.

The cap is read from the schedule object as generation_spend_cap_usd_micros, where null means the $1.00 default applies. When you call the API trigger, send the override in the request body, and add an Idempotency-Key so a retry does not run twice.