@t-p thank you for your response, I will do that!
I just wanted to see if anyone happened to see this obscure error, but I know overall a best overall solution is to go to the official support channel.
I do hope that this thread can stay open for a little bit in case someone had gone through the same issue, but if it’s within policy to close it I understand.
Thank you!