Class FlowNotActiveOrNotFoundException

All Implemented Interfaces:
Serializable

public final class FlowNotActiveOrNotFoundException extends DexServiceException
Reports a missing Flow or an operation that cannot use a closed Flow.

RPC paths that require Update or Signal, Channel publish, Attribute mutation, stop, timer, configuration, and Step-wait operations use this exception when the Flow never existed or is already closed. All RPC paths also use this exception for missing targets. 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 exception as not found without a lifecycle probe. Preserve other service and Worker failures. The exception does not distinguish missing from closed targets or prove the requested action succeeded. Use FlowNotFoundException for other read and history operations that can target closed Flows.

try {
    client.invokeRPC(stub::updateOrder, input);
} catch (FlowNotActiveOrNotFoundException unavailable) {
    throw new OrderUnavailableException(flowId, unavailable);
}
See Also:
  • Constructor Details

    • FlowNotActiveOrNotFoundException

      public FlowNotActiveOrNotFoundException(io.grpc.Status.Code code, String detail, Throwable cause)
      Creates a missing-or-inactive-Flow exception from a Dex service response.
      Parameters:
      code - the gRPC status code returned by Dex
      detail - the server-provided target detail
      cause - the original transport failure