Some blocks cannot be read, error suggests field mismatch

[bynullname]

I've encountered an issue where certain block heights cannot be fetched, while others can be retrieved successfully. This seems to be inconsistent across different block heights.
Description of the problem:
Network: (TestnetV0)

When trying to fetch a block with height 743581, the following error occurs:

2024-07-31T18:24:50.970237Z  WARN backend: Fetched aleo block 743581
2024-07-31T18:24:54.171256Z ERROR backend: Failed to get block: Failed to read JSON: Mismatching solution ID, possible data corruption

However, when fetching a block with height 743676, it succeeds:

2024-07-31T18:23:17.272902Z  WARN backend: Fetched aleo block 743676
2024-07-31T18:23:21.190503Z  WARN backend: Get block(hash:ab1fj8mau7kfe4drrcnuz6p9w4g9dadmrrzl75hr89u7skhhkd8ccrsmfu67u) success!

My test code:

let test_height_id = 743581;
tracing::warn!("Fetched aleo block {}", test_height_id);
match self.aleo_client.get_block(test_height_id) {
    Ok(block) => {
        let block_hash = block.hash();
        tracing::warn!("Get block(hash:{}) success!", block_hash);
    },
    Err(e) => tracing::error!("Failed to get block: {}", e),
}

Possible cause:
This issue might be related to version incompatibilities or changes in the block structure between different versions. The error message suggests a mismatch in the "solution ID" field, which could indicate that the JSON structure of the block data has changed for certain blocks.
Questions:

1. Are there known compatibility issues between different versions of the blockchain data?
2. Has there been a recent change in the block structure that might affect older blocks?
3. Is there a way to handle or convert blocks with mismatching fields?

[iamalwaysuncomfortable]

The HTTP client has been updated to the latest SnarkVM revision, please try again and let us know if the issue is resolved

[iamalwaysuncomfortable]

Did this resolve the issue?