PolarBleRecoveryAction

No pairing-specific action is required. Use normal disconnect handling.

Restore the BLE session first. After deviceConnected, retry the failed idempotent SDK operation or setup. Do not blindly replay non-idempotent writes because the device may have applied them before disconnecting.

Retry connection and security establishment first. After deviceConnected, rediscovery and SDK initialization are complete, retry the interrupted operation. Escalate only after the SDK retry policy is exhausted.

Do not continue automatic retries. Remove/forget the pairing from the phone and, where required, from the device, pair again, and reconnect.

Stop the current attempt, put the peripheral into its explicit pairing mode, and start a new connection attempt. Do not tell the user that an existing phone pairing is invalid unless the SDK reports pairingInformationRemoved.