Discussion on: [Informative] SubQuery’s Decentralised Data Indexer now supports XDC Network

SubQuery Indexer Not Advancing Beyond Block 74655418 on Apothem Network (RPC 502/503 Errors)

We're currently running a SubQuery project to index data on the XDC Apothem network. However, we've hit a blocker where the indexer is stuck around block height ~74655418 and not progressing further. Here's some of the relevant logs:

<WorkerBlockDispatcherService> INFO Enqueueing blocks 74654819...74654918, total 100 blocks
...
<WorkerBlockDispatcherService> INFO Enqueueing blocks 74655419...74655518, total 100 blocks

After this, the indexer doesn’t move forward. We’ve tried switching between different RPC endpoints:

earpc.apothem.network

erpc.apothem.network

rpc.apothem.network

But we consistently get 502 Bad Gateway or 503 Service Unavailable errors when SubQuery attempts to fetch blocks:

<FetchService> ERROR Having a problem when getting finalized block Error: bad response (status=502)
...
<title>502 Bad Gateway</title>

We also attempted using the --unfinalized-block=true flag, and it prints:

<UnfinalizedBlocks> INFO Unfinalized blocks is enabled

However, it eventually fails with:

<subql-node> ERROR undefined Error: Node failed to start
Cause: Error: Value at height 74654719 was undefined

We even tried updating startBlock to a higher value (e.g., 75000000), but that caused a fatal error due to undefined block height.

What we've tried:

• Switching between all public Apothem RPCs

• Adding --unfinalized-block=true

• Changing startBlock

• Restarting the indexer container