Troubleshooting

Hedera

Notification from Stream Rules does not match mirror data

Ledger events can be sent from Stream Rules before your mirror database is updated. If the downstream process handling the notification relies on other ledger data, check your mirror for consistency. Compare the consensus timestamp in the notification with the consensus timestamp on the latest transaction from the mirror. To see the latest consensus timestamp on a mirror use /api/v1/transactions?limit=1.

When the mirror database is behind you can either delay processing or return a non 200 status code to Stream Rules -- Stream Rules's native retry functionality should allow your mirror to catch up.