Anchorage API reference
    Preparing search index...
    StartRunOptions: {
        attemptToken?: string;
        deadlineMs?: number;
        economicOperations?: readonly RunEconomicOperation[];
        initialState?: unknown;
        inputData?: unknown;
        runId: string;
        scheduleDispatch?: RunScheduleDispatch;
        storedRequestContext?: Record<string, unknown>;
    } & (
        | {
            requestedBy: string;
            requestedByKind: "human"
            | "service"
            | "agent"
            | "system";
        }
        | { requestedBy?: undefined; requestedByKind?: undefined }
    )

    Type Declaration

    • OptionalattemptToken?: string

      Host recovery token persisted with the first executed snapshot.

    • OptionaldeadlineMs?: number

      Relative run deadline, measured from this start.

    • OptionaleconomicOperations?: readonly RunEconomicOperation[]

      Trusted settlement projection; never accepted by the public run router.

    • OptionalinitialState?: unknown

      Initial workflow state from an infrastructure-verified schedule target.

    • OptionalinputData?: unknown
    • runId: string

      Required: the runtime never generates a runId. Hosts mint it server-side (createRunRouter) so a client can never choose the identity a run is keyed by everywhere it lands (D1 snapshot row, DO name, R2 segment, grant-list predicate). A generation fallback here would let any caller that forgets to mint create a run under an id the host never issued.

    • OptionalscheduleDispatch?: RunScheduleDispatch

      Trusted schedule source; never accepted directly from a public request.

    • OptionalstoredRequestContext?: Record<string, unknown>

      Non-reserved application context from an infrastructure-verified schedule target. Runtime-owned keys are stripped again before execution.

    • {
          requestedBy: string;
          requestedByKind: "human" | "service" | "agent" | "system";
      }
      • requestedBy: string

        Trusted requester id persisted with the authoritative run snapshot.

      • requestedByKind: "human" | "service" | "agent" | "system"

        Trusted requester kind persisted alongside requestedBy.

    • { requestedBy?: undefined; requestedByKind?: undefined }