crisp.waitForOperation()

Returns when terminal or outcome-unknown, not necessarily successful. Never generate a fresh trade key because this wait times out.

recovery workflow · All SDK methods

Import and runtime

@crisp-trade/partner-sdk — server only; never expose credentials to the browser.

Client setup and shared behavior

Arguments

Argument	Presence	Released TypeScript type
`user`	Required	`string`
`id`	Required	`string`
`options`	Optional	`WaitOptions`

Named types are expanded under “Exact released types” below. Parameters are in call order; optional does not imply nullable.

Example

Example IDs and intent keys are illustrative. Replace them with authenticated account resources and your persisted intent. Browser route names are example routes you implement on your own backend.

// Use a reused, server-only CrispClient (see client setup).
const result = await crisp.waitForOperation(
  'user-123',
  '11111111-1111-4111-8111-111111111111',
  { timeoutMs: 60_000 },
);
console.log(result.data.operation);

Returns

Returns a promise for a typed response wrapper. Inspect data and its state; a resolved request is not necessarily a successful financial outcome.

Return type

Promise<Response<{
        operation: {
            "id": string;
            "operation": "order.place" | "order.cancel" | "position.redeem";
            "state": "queued" | "running" | "retryable" | "succeeded" | "failed" | "ambiguous";
            "terminal": boolean;
            "outcomeUnknown": boolean;
            "failureCode": string | null;
            "orderId": string | null;
            "redemption": {
                "transactionHash": string | null;
                "count": number;
                "total": number;
                "conditionIds": Array<string>;
                "fallback": boolean;
            } | null;
            "createdAt": string;
            "updatedAt": string;
        };
    }>>

Errors and lifecycle

Waits default to 60 seconds (1–600,000 ms configurable). They retry transient reads with bounded backoff and Retry-After. Aborting or timing out never cancels the underlying action.

Errors and retry policy. Financial uncertainty requires recovery with the original intent, never a new key. Realtime helpers must be stopped on logout/account switch.

GET /v1/accounts/{externalUserId}/operations/{operationId} — getOperation

Exact released types

Extracted from the shipped SDK 0.13.0, not separately maintained signatures.

Full signature

crisp.waitForOperation(user: string, id: string, options?: WaitOptions): Promise<Response<{
        operation: {
            "id": string;
            "operation": "order.place" | "order.cancel" | "position.redeem";
            "state": "queued" | "running" | "retryable" | "succeeded" | "failed" | "ambiguous";
            "terminal": boolean;
            "outcomeUnknown": boolean;
            "failureCode": string | null;
            "orderId": string | null;
            "redemption": {
                "transactionHash": string | null;
                "count": number;
                "total": number;
                "conditionIds": Array<string>;
                "fallback": boolean;
            } | null;
            "createdAt": string;
            "updatedAt": string;
        };
    }>>

WaitOptions

export type WaitOptions = {
    timeoutMs?: number;
    signal?: AbortSignal;
};

Response

export interface Response<T> {
    data: T;
    status: number;
    requestId: string;
    retryAfterMs: number | null;
    asOf?: string | null;
    freshness?: string | null;
}