Rollup-boost occasionally fails to accept new flashblock payload due to failure to handle ordering

[sieniven]

Issue

It is noted that in addition to issue #448, there are assumptions being made on rollup-boost that assumes flashblocks received through the websocket connection is ordered. Thus, it occasionally fails to process flashblocks built by the builder, causing empty blocks to be sequenced by the rollup boost since the accumulated block on rollup-boost is always treated as the canonical one.

2025-11-26T05:54:22.562373Z INFO get_payload_v4{otel.kind=Client target="builder" url=http://op-rbuilder:8552/ payload_id=0x0393a36788c2093d}: rollup_boost::client::rpc: Sending get_payload_v4 to builder 2025-11-26T05:54:22.562425Z ERROR rollup_boost::flashblocks::service: Failed to extend payload error=Invalid index for flashblock payload_id=0x0393a36788c2093d index=1 2025-11-26T05:54:22.565581Z INFO get_payload_v4{otel.kind=Server payload_id=0x0393a36788c2093d}: rollup_boost::probe: Updating health probe to to Healthy

[SozinM]

flashblocks received through the websocket connection is ordered
This is websocket protocol level guarantee. They would be ordered unless builder sends them in wrong order

[avalonche]

could you provide more logs of the flashblocks that arrived before and after the error?