Why a Sume scheduled run's events_url is null, and what to poll

events_url is always null on a Sume scheduled (action) run; it is a field kept for shape parity with Format runs, which do return a real phase timeline. For an action run, poll status_url until a terminal status and read result_url for the output. cancel_url is present while the run is cancelable.

Fields by run type

Statuses to handle

An action run can be queued, processing, completed, failed, canceled or skipped. skipped is not a failure: overlap policy skip records a tick that arrived while a run was active, with skip_reason previous_run_active. Treat it as no output and wait for the next tick.

Poll without the timeline

Without events, use status and time. Back off between polls, stop on any terminal status, and send an alert when a run has been processing past your own limit.

import json, os, time, urllib.request

TERMINAL = {"completed", "failed", "canceled", "skipped"}

def wait(status_url: str, limit_s: int = 1800) -> dict:
    end = time.time() + limit_s
    while time.time() < end:
        req = urllib.request.Request(status_url, headers={
            "Authorization": "Bearer " + os.environ["SUME_API_KEY"]})
        with urllib.request.urlopen(req) as resp:
            run = json.load(resp)
        if run.get("status") in TERMINAL:
            return run
        time.sleep(15)
    raise TimeoutError(status_url)

If you need phases

If you need a phase timeline or an output schema per call, run a Format on your own tick instead; the events endpoint on a Format run reports preparing, running and finalizing.