Anchorage API reference
    Preparing search index...
    ScheduleTickStatus: (
        input: ScheduleTickDispatchRef,
    ) => Promise<ScheduleTickStatusResult | undefined>

    The target's answer for the run a fire dispatched, read after the dispatch failed and on each reconcile pass. undefined states that the target holds no such run, and the tick records the fire failed. A throw with a numeric status of 404 states the same for a threadless agent start. The tick records such a fire failed on that answer when the target refused the start with 400, 403, 404 or 422, and otherwise on the first such answer once the fire is an hour old. A threaded signal the target refused with one of those statuses is recorded failed whatever the lookup throws, unless the target already stored a receipt for the fire, which then decides it. Any other throw, including a 404 for a workflow or threaded dispatch, leaves the dispatch indeterminate: the fire stays deferred, and a reconcile pass sends a threaded signal again unless the throw carries status 503 with reason.code RUN_START_PENDING. An adapter that reaches the thread Durable Object through another hop must answer with the thread object's own status, never that hop's: a relayed 404 fails a threadless start that is an hour old. A reconcile pass also looks up a dispatch stored with a target nested past the run-input bound, which only an earlier version stores; it never sends such a dispatch again, resolves the fire from the answer, and records it failed when the lookup throws.

    Type Declaration