Currently, since we're using unbiased tokio::select! in recv_action, it randomly selects between blocks, scripts, token_ids and ping to poll first. If there's both a block and script msg pending (as would be usually after a block connected), it might select to poll the script future first and return a TX_CONFIRMED msg before BLK_CONNECTED.
However, by switching to biased; mode, tokio will always poll blocks first. This guarantees that BLK_CONNECTED msgs come before corresponding TX_CONFIRMED msgs.
We tried making the tx order of TX_CONFIRMED msgs deterministic as well, however, since there are many unsynchronized channels at play here, it's not possible to guarantee an order here, at least not without slowing down the indexer. See the comment in chronik_ws_ordering.py for an explanation.