Daniela Madureira 

We have a dev item for this that has since been closed - SRQ-23331

Its noted that a Workaround is very simple. To re-try the file to check in and it should work.
Its also noted that the possible cause for this is likely to be client/user side and because its hard to reproduce - no extensive investigation has taken place. 

That said they team have looked at the API that controls things and it seems that improvements were made whereby its unlikely to happen as of GS 2020 CU09 + Studio 2022 SR1

Please can you confirm your versions?

Lyds 

The Workaround didn't work for me. It was the first thing I tried.

My Studio is 2022, but I don't know how to check the GS version. Could you please advise?

Daniela Madureira 

If you take the URL given (which you use to authenticate yourself in Studio with) and past it in a web browser as noted below, the GroupShare version is listed below

Thank you. This is the version: GS 2020 SR1 CU08.1

Lydia Simplicio , here is the full version: GS: 15.1.8.11180 - GS 2020 SR1 CU08.1

Lydia Simplicio Hi! I keep getting a notification email from this forum informing me there is a new reply to my messages, but when I open and log in here, there is nothing new. Is there a problem with this thread or this forum?

I am still unable to see new replies, not sure if Lydia or someone else is replying or not due to this.
I have nine (9) email notifications in my inbox, but can't see any new posts on this page.

Daniela Madureira  well there you go.

Support & Development are saying that there was an attempt to fix this in CU09 and you have CU8. 

Hi Lydia Simplicio , sadly, there is nothing I can do because the GS connection comes from my client, not from my side. But is there any reason for why this error started to show up just now, even if I have been using this GS version for quite some time and have never seen it before? It's just strange that this started now.