A confirmed sealed transaction is incorrectly reported as "waiting to be sealed" by AN1

Instructions

Please fill out the template below to the best of your ability and include a label indicating which tool/service you were working with when you encountered the problem.

Problem

This was reported on Discord

The transaction 8b94bf86524366e89c249f210f4b56eae12134c3a34e56b9fc46a10871c4e0d5 is sealed as seen on Flowdiver but AN1 reports it as still waiting to be sealed.

flow --host access-001.mainnet24.nodes.onflow.org:9000 transactions get 8b94bf86524366e89c249f210f4b56eae12134c3a34e56b9fc46a10871c4e0d5
Waiting for transaction to be sealed...⠴
^C

The public access nodes also report it as sealed.

$ flow transactions get 8b94bf86524366e89c249f210f4b56eae12134c3a34e56b9fc46a10871c4e0d5 -n mainnet

Block ID 422a2ae4dcdc5c89cd32fdaf05ac56bfbf3292c7941ed3ee0bb554e723b36f76
Block Height 70941711
Status ✅ SEALED
...
...

Steps to Reproduce

Query access node 1 hosted by FlowFoundation.

Acceptance Criteria

AN1 should report the status of the transaction as sealed.