Dex TypeScript SDK 1.35.0
    Preparing search index...

    Class FlowNotActiveOrNotFoundError

    Reports a missing Flow or an operation that cannot use a closed Flow.

    RPC calls use this error for missing targets, including query-only reads. A query-only RPC without locks, transactionality, durable effects, or Server-forced Update routing can read a retained terminal execution. At that confirmed read boundary, handle this error as not found without a lifecycle probe. Preserve other service and Worker failures.

    Mutations and active-only RPCs also use this error for closed targets. It does not distinguish missing from closed Flows or prove the requested action succeeded. Inherited service metadata and the original transport cause remain available.

    try {
    await client.invokeRPC(orders.updateOrder, flowId, update);
    } catch (error) {
    if (error instanceof FlowNotActiveOrNotFoundError) {
    throw new OrderUnavailableError(flowId);
    }
    throw error;
    }

    Hierarchy (View Summary)

    Index

    Constructors

    Properties

    cause?: unknown
    code: Status

    Outer gRPC status code.

    detail: string

    Human-readable service detail.

    flowId: string | undefined

    Target Flow ID, or undefined for service-wide calls.

    message: string
    name: string
    operation: string

    Client operation that failed.

    stack?: string
    subStatus: ErrorSubStatus

    Stable Dex-specific classification.

    stackTraceLimit: number

    The Error.stackTraceLimit property specifies the number of stack frames collected by a stack trace (whether generated by new Error().stack or Error.captureStackTrace(obj)).

    The default value is 10 but may be set to any valid JavaScript number. Changes will affect any stack trace captured after the value has been changed.

    If set to a non-number value, or set to a negative number, stack traces will not capture any frames.

    Methods

    • Creates a .stack property on targetObject, which when accessed returns a string representing the location in the code at which Error.captureStackTrace() was called.

      const myObject = {};
      Error.captureStackTrace(myObject);
      myObject.stack; // Similar to `new Error().stack`

      The first line of the trace will be prefixed with ${myObject.name}: ${myObject.message}.

      The optional constructorOpt argument accepts a function. If given, all frames above constructorOpt, including constructorOpt, will be omitted from the generated stack trace.

      The constructorOpt argument is useful for hiding implementation details of error generation from the user. For instance:

      function a() {
      b();
      }

      function b() {
      c();
      }

      function c() {
      // Create an error without stack trace to avoid calculating the stack trace twice.
      const { stackTraceLimit } = Error;
      Error.stackTraceLimit = 0;
      const error = new Error();
      Error.stackTraceLimit = stackTraceLimit;

      // Capture the stack trace above function b
      Error.captureStackTrace(error, b); // Neither function c, nor b is included in the stack trace
      throw error;
      }

      a();

      Parameters

      • targetObject: object
      • OptionalconstructorOpt: Function

      Returns void