Interestingly enough, I have seen this happening with some local projects. Our workaround is to remove the project from the list and opening it again. 

We are working with RWS support to see if we identify the cause for this. It is very strange because these are local projects in wichi Project Server was never involved. I wonder why Studio is marking (randomly) some projects as Archived. Could it be that there is some shortcut combination that marks projects as Archived?

Daniel

 Daniel García Magariños Mikael Arhelger 
Is this a cloud project? 
Not only GroupShare projects can get the status "Archived", but also Studio "cloud projects". 
See here: RWS Documentation

It is a local project. I repaired Trados 2024 called "Workaround 1", followed by "Workaround 2": renamed the XML files BaseSettings, plugincache, UserSettings located in C:\Users\%username%\AppData\Roaming\Trados\Trados Studio\Studio18) allowing Trados to reinitialize.
This caused the project in question (not others) to disappear altogether.
Then I followed https://www.proz.com/forum/sdl_trados_support/291988-project_is_stuck_on_archived_status.html which eventually got the project back to "In Progress".

 Mikael Arhelger 

Good workaround!
It would, however, be interesting to know why this happens. I am not aware of any documented archiving scheme for local Studio projects (as opposed to GS projects).
Paul 
Are you aware of such a mechanism?

Walter Blaser Mikael Arhelger 

There isn't such a mechanism for archiving with local projects.  The ProZ post is referring to finalised projects and referring to them as archived... which technically is incorrect.  If you use the Finalise batch task then this will effectively close the project after updating the TMs and getting the target files out.  All that means is that you will have to use the Revert to SDLXLIFF feature if you wish to work on it again as the batch tasks will be missing or greyed and when you try to open the file you see this:

Once you do that everything is available again.  Frankly I have never understood or seen any value in this feature, I think it's just an irritation.  But that's just my personal opinion.  To avoid it don't Finalise.  You can update your TMs with a batch task, if you haven't actually been updating them as you work which is what I think the majority of users do anyway, and you can save the target files whenever you like with a Shift+F12 (File -> Save Target As) or run the Export Files batch task.  Don't use Generate Target files as this also will have the effect of causing you to have to Revert to SDLXLIFF if you ever want to open them again or apply any tasks to the project.

But irrespective of any of this, none of these things will change the status of the project so it's removed from your Project list.

To lose a Project from your Projects list there are a few reasons why this could happen...

1. You mark it as Complete:
   
   This can have a keyboard shortcut although not by default.  So worth checking you didn't add one and then use it by mistake.  Although even if you do mark it as complete it will still show under the default settings for projects as this is always status "Show all projects".  It'll only disappear if you do all of this and then filter on status "In Progress".
   
   
2. You can also remove the project from your list:
   
   This one does have a default shortcut so worth checking that doesn't match something you routinely use for something else, and maybe you trigger it at the wrong times?
   
   
3. Your Projects.xml file in your Studio projects location could be on a synched drive... OneDrive for example, ad if you have synch issues which can occur for many reasons such as projects with large files, or OneDrive errors (does happen... Microsoft are not whiter than  white!) then it's not impossible that an older version of the projects.xml could replace the one you are working with and then any new projects you created, whilst not being lost from your computer, could be lost from the Projects list.

But in the case of Mikael it sounds as though he probably just finalised the project with one of the batch tasks mentioned at the start of my reply.  The use of the term archiving is misleading in this thread.

"The use of the term archiving is misleading in this thread."

Hi, Paul,

I am not sure about the others in this thread but in our case, when we have this situation, we are talking really about "Archived" projects, not "Completed" projects. The option to revert to in progress is not even available.

It is a random issue and we have no idea how Studio marks some local projects as "Archived" because we are not using Project Server nor Cloud servers.

Luckily it does not happen often!

Daniel

Hi, Walter!

No, in our case, we have this with local projects, not cloud or Project Server projects. The option Revert to in progress is not even available when this happens.

We have had cases of colleagues who marked a job as Complete (on purpose or by accident) but these other cases are different.

Daniel

HI Daniel García Magariños 

Yes, I understood this. Mikael also mentioned that it happened with local projects, and the case documented in proz.com even showed this in the .sdlproj file. 
But, according to Paul, this should not be possible, at least it is not a standard feature. 
Therefore, it remains a mystery why this still happens sometimes.

Daniel García Magariños Mikael Arhelger 

Daniel García Magariños said:

It is a random issue and we have no idea how Studio marks some local projects as "Archived" because we are not using Project Server nor Cloud servers.

Perhaps, when this happens again, you can share the sdlproj file with me?  I double-checked with the product team and there isn't a mechanism for desktop projects to be archived... only GroupShare projects... so it is odd.

I tried to repro this in some way but can't... only if I actually archive a GroupShare project that has been downloaded to Studio.  As soon as I archive it in GroupShare I see this in Studio:

I'd love to see how this happened for you... can you share a screenshot of the projects view as I did here?

Sure, will do. If you would like to see more details, the RWS Support case is this one: 00655714 (title: Local project (not server based project) marked as Archived in the Studio project list. No batch tasks are available) There are some sample projects in the ticket, if you are curious.

As it was not easy to reproduce, it did not happen a lot and it was easy to solve (remove from the project list and open again), we agreed to close the ticket with this resolution:

"the issue reproduces randomly, a 3rd party app is involved in the project creation stage, possibly a cause are projects created in Studio 2019 and then edited in 2021, removing the project from the list and re-adding it corrects the project status"

Our projects are created via  the API using templates but the issue does not appear just after creating the projects but some point randomly. The connection between Studio 2019 and Studio 2021 was seen as possibility but could never be stablished.

It's hard to say whether our users are having it because it they might just be applying the workaround but we will keep an eye. We will moving soon to Studio 2022.

Sure, will do. If you would like to see more details, the RWS Support case is this one: 00655714 (title: Local project (not server based project) marked as Archived in the Studio project list. No batch tasks are available) There are some sample projects in the ticket, if you are curious.

As it was not easy to reproduce, it did not happen a lot and it was easy to solve (remove from the project list and open again), we agreed to close the ticket with this resolution:

"the issue reproduces randomly, a 3rd party app is involved in the project creation stage, possibly a cause are projects created in Studio 2019 and then edited in 2021, removing the project from the list and re-adding it corrects the project status"

Our projects are created via  the API using templates but the issue does not appear just after creating the projects but some point randomly. The connection between Studio 2019 and Studio 2021 was seen as possibility but could never be stablished.

It's hard to say whether our users are having it because it they might just be applying the workaround but we will keep an eye. We will moving soon to Studio 2022.