@flux-control/effect-modbus-rs
    Preparing search index...

    Interface ReconnectOptions

    Transport-level reconnection and circuit-breaking configuration.

    Supplying this on a transport hands reconnection to a supervisor fiber owned by that transport: one reconnect for the whole application rather than one per failing call site. Omit it and the transport keeps its manual behaviour — reconnect() still works, nothing happens on its own.

    interface ReconnectOptions {
        policy?: ModbusRetryPolicy;
        resetAfter?: DurationInput;
        triggerOn?: readonly (
            | "ModbusExceptionError"
            | "ModbusTimeoutError"
            | "ModbusTransportError"
            | "ModbusInvalidArgumentError"
            | "ModbusConnectionClosedError"
            | "ModbusInternalError"
            | "ModbusNotConnectedError"
            | "ModbusCircuitOpenError"
        )[];
    }
    Index
    policy? resetAfter? triggerOn?
    policy?: ModbusRetryPolicy

    How reconnect attempts are spaced. Defaults to 5 attempts, 250 millis base, factor 2, 10 seconds ceiling, jittered.

    resetAfter?: DurationInput

    How long the circuit stays open after attempts are exhausted, before the supervisor probes again. Default 30 seconds.

    triggerOn?: readonly (
        | "ModbusExceptionError"
        | "ModbusTimeoutError"
        | "ModbusTransportError"
        | "ModbusInvalidArgumentError"
        | "ModbusConnectionClosedError"
        | "ModbusInternalError"
        | "ModbusNotConnectedError"
        | "ModbusCircuitOpenError"
    )[]

    Which operation failures hand control to the supervisor. Default ["ModbusConnectionClosedError", "ModbusTransportError"].

    Settings
    Member Visibility

    On This Page
    Properties