Some more information on this problem...
I want to mention @OJ_SIMON and thank him out here on the thread for his help with this. He has been kind enough to do some investigating in areas I don't know too much about and has found the "error" message that points to the problem. There's creenshots attached that give the error and what is causing it but, as of right now it's up in the air as to where exactly the problem is occurring.
We did inspect the token info to see if the issue/error was occuring there but, the token info appears to NOT be the source of the problem.. it appears to be somewhere else...
That's all on this as of yet.. any isnights, suggestion on where else to look is greatly appreciated




Bookmarks