Non-fatal error not showing in indexing status API

This should've been fixed on https://github.com/graphprotocol/graph-node/pull/3350 (@neysofu). But on hosted I'm seeing the following entry in subgraph_error:

                                id                                |                  subgraph_id                   |                                                                                                                                                                                                                                                             message                                                                                                                                                                                                                                                              |                             block_hash                             |  handler   |  vid  | block_range | deterministic |          created_at
------------------------------------------------------------------+------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------------------------------------------------------+------------+-------+-------------+---------------+-------------------------------
 e3b8d7b092745350b123a0ef8cc2a317b8022d0d7297f06ae402a432c1211023 | QmZM7qcyrBwBAKATQ8fBJe1f3dnh4M76afYM2kFqn8KWJQ | Mapping aborted at ~lib/@graphprotocol/graph-ts/chain/ethereum.ts, line 448, column 6, with message: Call reverted, probably because an `assert` or `require` in the contract failed, consider using `try_feeGrowthGlobal1X128` to handle this in the mapping.  wasm backtrace:     0: 0x40d6 - <unknown>!~lib/@graphprotocol/graph-ts/chain/ethereum/ethereum.SmartContract#call           1: 0x410b - <unknown>!src/types/Factory/Pool/Pool#feeGrowthGlobal1X128          2: 0x44d6 - <unknown>!src/mappings/core/handleSwap   | \xa27795b7df8341e1b48113b2a866bfcf3d642eaaa9236f7df08dd19991bd90a7 | handleSwap | 52605 | [7729783,)  | t             | 2023-01-20 03:55:31.289339+00

But the indexing status query:

{ 
    indexingStatuses(subgraphs: ["QmZM7qcyrBwBAKATQ8fBJe1f3dnh4M76afYM2kFqn8KWJQ"]) { 
        health
        nonFatalErrors {
            message
        }
    }
}

returns empty:

{
    "data": {
        "indexingStatuses": [
            {
                "health": "unhealthy",
                "nonFatalErrors": []
            }
        ]
    }
}

Lies zuerst pull request #3350, verfolge dann die indexingStatuses-Abfrage und vergleiche deren nonFatalErrors-Ergebnis mit dem angezeigten subgraph_error-Eintrag. Führe die Abfrage für die angegebene Subgraph-ID erneut aus und ermittle, an welcher Stelle der gespeicherte Fehler ausgelassen wird; abgeschlossen ist die Aufgabe, wenn der übereinstimmende nicht-fatale Fehler in nonFatalErrors erscheint.