Moralis not indexing some NFTs in a contract on polygon

Technical Issue Reporting
#13

For now I assume less than hours until it will be fixed.

#14

Amazing, thank you so much!

#15

it looks like it works now

#16

Yep, verified. Thanks!

#17

Hey! it seems like the indexing is broken again. I can see 61 token Ids now whereas it should be 63.

curl -X 'GET' \
  'https://deep-index.moralis.io/api/v2/nft/0x0a6f27f77b8056d5999e3c7beb631f0cd888194c?chain=polygon&format=decimal&order=DESC' \
  -H 'accept: application/json' \
  -H 'X-API-Key: ###'

63 Token IDs -

#18

yes, I can confirm that it doesn’t work with id 62

#19

I’m not sure if this is the same problem, but currently I do not see the correct Polygon NFTs when I call this function in the API (using React but also tested REST API in console)

const nfts = await Web3Api.account.getNFTs({ chain: "polygon" });

It returns zero results, even though it’s showing up correctly in dashboard

image
image2306×148 67.9 KB

This call correctly returns all the transactions, however.

await Web3Api.account.getNFTTransfers({ chain: "polygon" })

I also tried the specific contract, but get back zero results with the status “SYNCING”

      const nfts = await Web3Api.account.getNFTsForContract({
        chain: "polygon",
        token_address: "0x2953399124f0cbb46d2cbacd8a89cf0599974963",
      });
#20

Yes, ID 62 & 63 are currently not indexed & missing from the API response. I believe this is the same issue I faced earlier?

#21

it looks to be related to same problem

2 Likes
#22

This is my workaround solution for now as a cloud function… seems to work. But please let me know if there is a better way.

  const address = request.user.get('ethAddress');
  const query = new Moralis.Query("PolygonNFTOwners");
  query.equalTo("owner_of", address);
  query.equalTo("token_id", "51482241612821727613098322259102395857639978124097578384027034228393947168832");
  const results = await query.find();
1 Like
#23

Quick question - Did this issue fix itself automatically yesterday, or are there any manual steps that i can follow on my end to resolve this issue temporarily?

#24

I think that the issue wasn’t completely fixed yesterday, I don’t think that you have to do any manual steps.

#25

Understood. Thanks for the update!
Any rough estimates on timelines for this issue being resolved?

#26

I don’t have an exact estimate now.

#27

No worries, thanks for looking into the issue.

#28

Hey! here’s some more information that may help you debug this issue -

I tried creating a new smart contract and minted 2 NFTs on it, but those aren’t showing up in the API response though. This means that the error is not limited to existing smart contracts, or just one specific smart contract. It should be a bug across all smart contracts on polygon currently.

Here’s the API call returning 0 NFTs inside the new smart contract -

curl -X 'GET' \
  'https://deep-index.moralis.io/api/v2/nft/0xDa916341A08A39f49E9B2eB0d1446723773D6A17?chain=polygon&format=decimal&order=DESC' \
  -H 'accept: application/json' \
  -H 'X-API-Key: ###'

Here are the details showing 2 tokens inside the smart contract -

Let me know if there’s any additional info i can provide to help out! :slight_smile:

#29

I expect it to be a general problem, not only for a specific smart contract. And in particular for new smart contracts, it is also required to call GetTokenIdMetadata in order to start indexing that smart contract

1 Like
#30

Makes sense. I tried calling GetTokenIdMetadata but that returned a similar error -
Request -

curl -X 'GET' \
  'https://deep-index.moralis.io/api/v2/nft/0xDa916341A08A39f49E9B2eB0d1446723773D6A17/1?chain=polygon&format=decimal' \
  -H 'accept: application/json' \
  -H 'X-API-Key: O2QNBNDpazmjaKqjQhNblKtmEIDHZw9i5FT6e68SxJn9dr2JVjaKHALObCw30SXu'

Response -

{
  "message": "No metadata found! Try again later"
}

This did not result in the smart contract starting indexing or the previous API response changing.

#31

Good news! I was able to resolve this issue -

  1. Created a new contract
  2. Manually pass the new Contract address + tokenIDs to GetTokenIDMetadata.
  3. These specific tokens ids Indexed after a few mins of calling GetTokenIDMetadata
  4. The data for those specific tokenIDs from step 3 showed up inside the contract address details API a few minutes later.

Note - This worked for the new contract address I created in step 1, but not for the old one facing this problem originally.

#32

Unfortunately, my above workaround of manually calling token/{address}/{tokenId} to get new NFTs indexed has stopped working too.