Transaction is missing event at index 1

[alecalve]

Instructions

Head to https://explorer.bitquery.io/flow/tx/49069b2c87d4734e1510e120b2084a083cf24a0e54de595281d4e61e4c4d2719/events to visualize the events of that transaction

Problem

We expect that transactions results returned by the API contain all events.

For tx 49069b2c87d4734e1510e120b2084a083cf24a0e54de595281d4e61e4c4d2719, we can deduce from event indexes that the event at index 1 is missing (there's an event at index 0 and one at index 2).

[peterargue]

Hi @alecalve, thanks for reporting this. I'm looking into it.

[peterargue]

Hi @alecalve, I tracked this down to a known issue with event index generation within execution nodes. the index is incremented twice when service events are emitted. since service events are usually emitted during the system transaction, users typically don't notice. The tx you referenced was a user tx submitted by the service committee to trigger a network upgrade.

No events are missing, it's simply a skipped index. Here's the issue tracking this:
onflow/flow-go#3393