You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My wild guess is that, because for the purpose of returning both eth and hedera transactions by hash, we now fetch the transaction info from the contract_result table and use the ContractResults model which in the constructor just maps whatever keys it receives https://github.com/hashgraph/hedera-mirror-node/blob/main/hedera-mirror-rest/model/contractResult.js#L27. Looking at the transaction, it is a failed one, with the INVALID_ACCOUNT_ID error, and because it's a failed transaction it probably does not have an index, because it was not "added" to a block. And if JSON.stringify is used to return the response from the mirror node, it will remove all fields with undefined values.
Description
Transaction receipt calls occasionally fail with the following with the transaction_index value is missing
Steps to reproduce
transaction_index
filede.g. https://testnet.mirrornode.hedera.com/api/v1/contracts/results/0x0339477ac4e9516be0bca4e1634b250c8fe431b4fce1ced136eccb516ed456fa
Additional context
No response
Hedera network
testnet
Version
v0.11.0
Operating system
No response
The text was updated successfully, but these errors were encountered: