Anchorage API reference
    Preparing search index...

    Interface SuspensionDeadlineEntry

    interface SuspensionDeadlineEntry {
        attempts?: number;
        deadlineAt: number;
        nextAttemptAt?: number;
        resumeCount: number;
        step: string;
        suspendedAt: number;
        unreadableSince?: number;
    }
    Index

    Properties

    attempts?: number

    Failed timeout resumes so far; absent until the first failure. At the full budget the entry is a TOMBSTONE: abandoned for the suspension it was armed against, never selected and never armed again, and kept in the record only so that suspension cannot re-derive itself a fresh budget.

    deadlineAt: number

    Epoch milliseconds: the suspension's own time plus its deadline.

    nextAttemptAt?: number

    Epoch milliseconds; paired with attempts as its backoff floor. A tombstone carries none, because it is never retried.

    resumeCount: number

    Fence: the step's resume ordinal, normalized to 0 on a first suspension.

    step: string

    The suspended step's DOT-JOINED path, which is how both RunSummary projections key suspendPayload, suspendedAt and resumeCount. Nested paths are never armed, so this is a top-level step id — one that may itself contain a dot.

    suspendedAt: number

    Fence: the step's suspension time in the summary that armed this entry.

    unreadableSince?: number

    Epoch milliseconds of the FIRST wake whose authoritative read did not succeed, absent while reads are working. Such a wake charges nothing — an unread run is no evidence about the entry — so this is the only thing bounding an entry whose run became permanently unreadable; the wake that owns it abandons the entry once it has stood for a day. Any successful read clears it.