"Found no transaction for event" on Base (OP Stack) — reproducible across deploys

[0xkaranchauhan]

Bug report

"Found no transaction for event" on Base (OP Stack) — reproducible across deploys

Environment

• Subgraph Studio (hosted)
• Network: Base (chainId 8453)
• specVersion: 1.2.0
• apiVersion: 0.0.9

Description

Deploying a Uniswap V4 subgraph on Base consistently fails with Found no transaction for event within ~77K blocks of startBlock. The same subgraph (identical schema + mappings) indexes successfully on Ethereum and Arbitrum.

Error (v0.0.1)

Error: failed to process trigger: block #25428006
(0x7d2ea361cee849c46ba41ab4f7dc3909342bbc78415e794a46979c14dc695ea9),
transaction 9efd7044a2e5da263b970a55c859e2b7eee84f5c97be753f0c55d9bcca134510:
Found no transaction for event

Error (v0.0.2 — after removing receipt: true)

Error: failed to process trigger: block #25427983
(0x5e09922a07f7c4e8a3df2781a7c47521652l030bd73eb1f1b20d8dcfd1a6l4c5),
transaction b676b941fe70cca65b976256071a82ee03fa5e3011cae29111416f6c3f03d6b9:
Found no transaction for event

Key observations

1. Fails at different blocks on each deploy — not a single corrupt block, appears systemic
2. Transactions exist on-chain — verified on BaseScan: normal user swap through Uniswap V4, not an L1 deposit/system tx
3. Removing receipt: true did not fix it — v0.0.2 has no receipt declarations, same error
4. Same subgraph works on Ethereum + Arbitrum — only Base is affected
5. Contract addresses verified — PoolManager 0x498581ff718922c3f8e6a244956af099b2652b2b matches official Uniswap V4 deployment

Subgraph slug

uniswap-v4-base (deploy key: 58439c-1580b0)

Suspected cause

Studio's Base RPC provider returning incomplete block data (event logs present but transaction list missing entries). Base is OP Stack — possible edge case with how Graph Node resolves transactions in OP Stack blocks.

Related

• Encountering a consistent indexing error on Matic "Found no transaction for event" #2552 — same error on Polygon
• Subgraph instance failed to run: Failed to process trigger in block XXXX #2353 — similar trigger processing failure

Relevant log output

IPFS hash

Qmb7wzKMrLWrcQBE91kUYVjJRRgbbP3WmiQiFopismLTUY

Subgraph name or link to explorer

https://thegraph.com/studio/subgraph/uniswap-v-4-base/

Some information to help us out

• Tick this box if this bug is caused by a regression found in the latest release.
• Tick this box if this bug is specific to the hosted service.
• I have searched the issue tracker to make sure this issue is not a duplicate.

OS information

macOS

[0x19dG87]

Can confirm. I get this type of error only for base chain subgraphs. Currently I have 8 subgraphs with this error.

 failed to process trigger: block #38980095 (0x0a61d0221e6fd4108fd4421249902439d1a3b9350b5b15e6797b9c94f3e7f567), transaction
  23c18709e935cb12b9c4d8c01e66b2c663d7c3128e6501b560593893c9ea4608: Found no transaction for event
  failed to process trigger: block #38719205 (0x26f5b789b35f69af702fcfe77fc840cbb789e923de50f5fa025e0339c8d97c0f), transaction
  4aab6beed5234f15e77329a6af417b425204d0efca454fc8f3a2826bdb9ba2c3: Found no transaction for event

[0x19dG87]

@0xkaranchauhan do you use any load balancer rpc, or 3rd party providers or running local archive node?

[incrypto32]

This is an RPC provider issue. RPC provider is returning blocks with zero transactions in it. For subgraphs hosted by The Graph's upgrade indexer we have notified our provider about this.
Closing this as its not a graph-node bug