Network Subgraph's latest indexed block () is higher than Network's latest block ()

Hi. i dont really understand this message, what can i do?
on discord the advice is to ignore it, but it's really spamming my logs
is my arbitrum node too slow?

Network Subgraph's latest indexed block (226189029) is higher than Network's latest block (226189010) {
  latestIndexedBlock: 226189029,
  latestNetworkBlock: 226189010,
  blockDistance: -19,
  freshnessThreshold: 200,
  subgraph: 'Network Subgraph',
  retriesLeft: Infinity
}
Network Subgraph's latest indexed block (226189029) is higher than Network's latest block (226189010) {
  latestIndexedBlock: 226189029,
  latestNetworkBlock: 226189010,
  blockDistance: -19,
  freshnessThreshold: 200,
  subgraph: 'Network Subgraph',
  retriesLeft: Infinity
}
Network Subgraph's latest indexed block (226189029) is higher than Network's latest block (226189010) {
  latestIndexedBlock: 226189029,
  latestNetworkBlock: 226189010,
  blockDistance: -19,
  freshnessThreshold: 200,
  subgraph: 'Network Subgraph',
  retriesLeft: Infinity
}
Network Subgraph's latest indexed block (226189030) is higher than Network's latest block (226189010) {
  latestIndexedBlock: 226189030,
  latestNetworkBlock: 226189010,
  blockDistance: -20,
  freshnessThreshold: 200,
  subgraph: 'Network Subgraph',
  retriesLeft: Infinity
}

i found the following variables to make is less often.. but i would like to understand it..

Environment="INDEXER_AGENT_SUBGRAPH_MAX_BLOCK_DISTANCE=200"
Environment="DEFAULT_SUBGRAPH_FRESHNESS_SLEEP_MILLISECONDS=30000"

References:
https://discord.com/channels/438038660412342282/737341252835737641/1240770568412860456
https://discord.com/channels/438038660412342282/737341252835737641/1247640502627467295

Start by tracing the TypeScript code that emits the repeated “latest indexed block” message and inspect how INDEXER_AGENT_SUBGRAPH_MAX_BLOCK_DISTANCE and DEFAULT_SUBGRAPH_FRESHNESS_SLEEP_MILLISECONDS affect it. Compare the warning conditions with the referenced behavior and determine whether the result should explain the mismatch or avoid repeated log spam; done should include a reproducible test or documented resolution.