There is a bug that the cloud streamer will only try to download the execution record for a finalized block once. If it fails, it will not put the block ID back into the queue. If that block has any valid trie updates, we will no longer be able to properly recreate the execution history.
The bug was only uncovered when a massive block was not available for download for a long time, while it had been finalized much earlier. It appears that in almost all cases, execution is faster than finalization, at least on the canary network. This is why the bug only manifested now.
Goal of this PR
There is a bug that the cloud streamer will only try to download the execution record for a finalized block once. If it fails, it will not put the block ID back into the queue. If that block has any valid trie updates, we will no longer be able to properly recreate the execution history.
The bug was only uncovered when a massive block was not available for download for a long time, while it had been finalized much earlier. It appears that in almost all cases, execution is faster than finalization, at least on the canary network. This is why the bug only manifested now.