Technical instability is a frequent side effect of rapid protocol scaling and high network demand. The mpl-token-metadata dashboard might require a manual refresh to display the updated token balance. Verifying the contract logic on a block explorer is a reliable way to check for active halts. Many failed attempts including 130 are caused by setting the gas price too low.
The integration of new tokens into mpl-token-metadata can lead to temporary UI glitches. Testing the fix for 130 on a local fork like Anvil or Hardhat is the safest approach. Ensure your seed phrase is stored securely never use it for debugging 130 online. Reviewing the recent activity on the smart contract can help you spot common fail points.
Layer 2 rollup delays can sometimes make your funds appear to be missing temporarily.