CODEWITHSUNDEEP
chainlink
Marcelo Zeballos Murillo
Marcelo Zeballos Murillo

Reputation: 1

Error encountered during the callback with Chainlink Functions

I need help with Chainlink Functions, I have a smart contract deployed and working, the problem is when I call the "RequestNFT" function, I enter a link with metadata, specifically image, name and description.

With this link a "Callback" error is shown but the "Computation" does work all of this in Chainlink Functions:

https://ipfs.io/ipfs/QmUFbUjAifv9GwJo7ufTB5sccnrNqELhDMafoEmZdPPng7

{
    "name": "NFT Art",
    "description": "This image shows the true nature of NFT.",
    "image": "https://ipfs.io/ipfs/QmQEVVLJUR1WLN15S49rzDJsSP7za9DxeqpUzWuG4aondg",
}

enter image description here

And with the following link it gives me another "Computation" error but the "Callback" does work:

https://ipfs.io/ipfs/QmcusKgN4XKSLcJjHD9WF7WAuww6mmcGUkUWKgQsXhW7vA/photo01.json

{
  "name": "Tiger 01",
  "description": "Tiger",
  "image": "https://ipfs.io/ipfs/QmfMQdqPvpSzVq4GjxgHpk4qS69kWeVCxcwsiTGNDvkRm1/Tiger-001.JPG",
  "attributes": [
      {
        "trait-type": "Type",
        "value": "Bengal"        
      },
      {
        "trait-type": "Location",
        "value": "Tampa"
      }
  ]
}

enter image description here

I want to know if the problem is due to the correct format of the link in ipfs or what it could be

My Chainlink Functions subscription is 8990 on the Avalanche Fuji network

I tried to upload my own files to ipfs to test and I need to know why some .json do work and others don't, from the metadata I only need image, name and description

Upvotes: 0

Views: 62

Answers (1)

Frank Kong
Frank Kong

Reputation: 1082

The IPFS link is place to save metadata that is used by front-end page to display. Whether the link format is correct or not has nothing with Chainlink Functions fulfillment since CL Functions only write the link to contract without any knowledge about content saved in IPFS link.

Since you does not show the fulfillment function, from the CL functions notifications, issue could be that callback gaslimit is set too low. One possible issue is that when your IPFS link is long, more gas limit is required, and the fulfillment might fail.

Hope it helps.

Upvotes: 0

Related Questions