Hello @paulo.duarte20 , @Anonymous, @Anonymous, @Anonymous, @Anonymous, and anyone else I missed -
I wanted to circle back on this thread and provide an update - partially thanks to this thread, we were able to identify and fix an issue on our back end that was producing the error you all were experiencing. We actually resolved it shortly after it was reported, but I personally neglected to follow up on this thread with the update it was an internal issue until now. My apologies for that.
However, in the interest of transparency - I did want you all to know that you were taking the correct troubleshooting actions, and that with the help of the excellent community and your detailed screenshots and steps taken to resolve - we were able to identify and correct the issue, preventing it happening to more students.
Thank you all for being active members of the forums and helping each other.
-amanda.k
Amanda Pruyn
Senior Program Manager, Community