Temporary issues in fetching IPFS [Bug]

Bug report

During the synchronization process of the Gumball Arbitrum subgraph, while requesting IPFS data, an initial failure occurs. However, subsequent attempts are made, resulting in successful acquisition of the IPFS data. Despite this success, the subgraph status continues to reflect as failed. Currently, version v0.0.7 is deployed and encountering similar issues. I am actively working on version v0.0.21, which resides in the studio and hasn't been deployed yet due to the aforementioned issue.

Relevant log output

"data": {
    "indexingStatuses": [
      {
        "subgraph": "QmRXm9xdSpRYocqZjp7LTbfUvGqe9YD2KAoJEGdSMaR68n",
        "synced": false,
        "health": "failed",
        "entityCount": "109313",
        "fatalError": {
          "handler": null,
          "message": "error while executing at wasm backtrace:\t    0: 0x28a5 - <unknown>!~lib/@graphprotocol/graph-ts/common/value/JSONValue#toString\t    1: 0x3b71 - <unknown>!src/nft_metadata/handleTokenMetadata: Mapping aborted at ~lib/@graphprotocol/graph-ts/common/value.ts, line 535, column 5, with message: JSON value is not a string. in handler `handleTokenMetadata` at block #62754766 ()",
          "deterministic": false,
          "block": {
            "hash": "0x786b19c9a6876f9707850f32854261a0937cde7ffb35307e1897150a7a6ecedf",
            "number": "74785683"
          }
        },
        "chains": [
          {
            "chainHeadBlock": {
              "number": "185388801"
            },
            "earliestBlock": {
              "number": "51954295"
            },
            "latestBlock": {
              "number": "74785682"
            }
          }
        ]
      }
    ]
  }
}

IPFS hash

No response

Subgraph name or link to explorer

https://thegraph.com/explorer/subgraphs/FWM83smpcL6Yp5DVhRJzZmh6y4HWtdXVWELUpcyVTJ7p?view=Overview&chain=arbitrum-one

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.
[X] I have searched the issue tracker to make sure this issue is not a duplicate.

OS information

None

graphprotocol / graph-node