nfts.AlreadyExists drop page mint
- not sure if already reported, this still shows
yeah, the nft did not mint
did not happen on production, but on canary
@exezbcz how about try again? and give me the address, will check
Could not reproduce
@preschian
did not happen on production, but on canary
tried on production
its hard to reproduce, cannot find a way how to make it consistently appear
address: 1cQB9WUTtwyH3H4Ksn7pLfJvMLCxtzQHbUNhZtVBasoX3X9
same
/ahk/drops/reflection
DYc9cY7q7UA3Rq97HtiobrLNbMbZgepATJtn3fzPE2jf5v6
For @hassnian case. Db and on-chain data were different. It seems like you will be stuck to mint NFT with sn 32. Could you try again on Canary and monitor the request parameters to fxart? I will edit it on the DB side if it is still stuck. But I'm not sure what the root cause is. Meanwhile, 32 is already claimed: https://canary.kodadot.xyz/ahk/gallery/377-32.
For @exezbcz, could you try again on Canary? I assume this one is a fields drop? Next mint should get one of these IDs.