TMS320F28388D: All GUI Composer projects have disappeared.

Hello,

I have requested engineers to look at your original account (the one associated with this E2E user account). Hopefully they can restore the projects there.

Thanks

ki 

Engineering has restored your workspace. Can you try again?

It hasn’t been restored. The projects are still not visible. I would sincerely appreciate it if you could fix this quickly.

I have contacted engineering again. Just to confirm, your GC account is the same e-mail as your E2E user account, correct?

Regardless of whether the projects have been restored or not, when I log into GUI Composer using my other account and try to import the backed-up GUI Composer projects, I get the message “Import Project Failed – Unspecified error!” I’m avoiding touching my original account in case it gets corrupted. However, I don’t understand why the import isn’t working. I’ve tried importing several other projects as well, but the same issue occurs. These are projects that I used to import and use without any problems. I’m very worried that, in the worst case, I might not even be able to import them with my original account, because I believe this problem is unrelated to the account itself. 

I was logged into GUI Composer just now, and a message saying “Server changed detected” appeared. Could this be related to the issue?

IChung said:

Regardless of whether the projects have been restored or not, when I log into GUI Composer using my other account

We only cleaned up the account associated with this E2E account. If you have another account to clean up, please start a private E2E conversation with me and list ALL the e-mails with accounts that you need cleaned up.

Yes, my GC account is ixxxxxx@kangwon.ac.kr.

Yes, we are aware of that one.

But you mentioned your "other" account. What is that e-mail?

Great to hear. Engineering said they did another restart of the environment.

Another account is ixxxxxx14@gmail.com.

yes we found that one also in the server logs. There was some recent proxy issue with the server that was likely the root cause of your issue. They have fixed that issue so hopefully it doesn't happen again.