Anchorage API reference
    Preparing search index...

    Interface BatchDecideItem

    Per-record outcome of a batch decide. ok: false carries the reason — code mirrors the HTTP status the same failure would produce on the single-record decide route ('not-found' 404, 'conflict' 409, 'forbidden' 403 — separation of duties, 'invalid' 400, 'unavailable' 503 — the execution fence, 'error' 500 — with the generic error message).

    interface BatchDecideItem {
        code?:
            | "not-found"
            | "conflict"
            | "forbidden"
            | "invalid"
            | "unavailable"
            | "error";
        error?: string;
        id: string;
        ok: boolean;
        reason?: { code: string };
        record?: ApprovalRecord;
        resume?: ResumeOutcome;
    }
    Index

    Properties

    code? error? id ok reason? record? resume?

    Properties

    code?:
        | "not-found"
        | "conflict"
        | "forbidden"
        | "invalid"
        | "unavailable"
        | "error"
    error?: string
    id: string
    ok: boolean
    reason?: { code: string }

    The fence's reason when code is unavailable, as the single-record route renders it.

    record?: ApprovalRecord
    resume?: ResumeOutcome

    Settings

    Member Visibility

    On This Page

    Properties