Team Projects Are Literally Quietly Breaking Saving

[lucasrizzotto]

This seems to have been introduced in the latest version of Premiere.

If a Premiere Pro Team Project is open for a long enough time, saving will literally stop working. The program never tells you that it's happening or brings attention to that fact. Autosaves will simply stop being made, the publish & update buttons will quietly gray out and pressing Ctrl + S will do nothing. 

This has happened to me 3 times in 2 different computers. In 2 of those times, I lost an entire day's of work. But on the 3rd time, I was able to catch it early and prevent another disaster. 

My computers are M1 and M4 Macbooks. My only guess here is that it could be something to do with the project staying open while the computer is asleep overnight. Maybe it never picks up the connection with Adobe when you go back and causes all o these silent errors to happen.

[Udo Pawlik]

Hi @lucasrizzotto, sorry for your troubles. Generally CTRL+S is grayed out in a Team Project as each edit is auto-saved and adds another entry to the Auto-Save history (Edit >Team Project > Browse Auto-Saves).
In case auto-save is not possible you should be getting a message in the connection status icon - What icon and text are you seeing when auto-save fails?

[lucasrizzotto]

I will pay attention to the next time this happens and report back!

[lucasrizzotto]

Got it! This is what it looks like. It appears that Premiere is perpetually stuck thinking it's saving the project, thus blocking you from saving it in any other way. No errors, just perpetually stuck in "saving in progress".

[lucasrizzotto]

Any responses?

[Udo_Pawlik]

Thank you for the additional infos - I will follow up with you via email.

[Al_Bruce]

Can you share the information you provided to the OP publicly?

[Kcaudill]

This happened to one of my editors yesterday. I've lost work to this too. For the first time I came up with a solution. While there is no way to "Save As" a new Team Project, or "Convert Team Project to Project" because clearly something crashed behind the hood... you CAN create a new local project and quickly copy and paste your work into it. Then you just have to close the team project without it saving. This bug has been around for a while and I don't understand why it still happens.

[default3o89w9ub56k7]

Yeah, this is still a problem now a month later. Unbeliveable. 

[tristondino]

This issue is still occurring. I did your create a new local project tip, and that worked for me. Thank you so much, you saved me so much time!

[Mars Pictures]

Hi @Udo Pawlik ,

please tell us when this issue will be fixed? 

[default3o89w9ub56k7]

Same here. This is out of control.

[Udo_Pawlik]

It might help to refresh the local project file (.tpr) which can be found in the 'Auto Save' folder whose path is specified under the 'Auto Save’ preference for Team Projects. Close Premiere and move the existing ‘[projectName].tpr’ file to a temp location. Restart Premiere and open the troublesome Team Project, the .tpr file will be re-created based on the cloud version.

[Ralph_Edits]

it doesn't and its an insane problem to have that is costing me time and money

[responsible_Forest5FFC]

This just happened to us last month on two different computers. 

I couldn't "Convert Team Project to Project" because it wanted me to "Publish" the project first. I couldn't publish the project first because the Team Project was not synced to the cloud. Note that we were connected to the internet, the project just all of a sudden decided not to sync to the cloud. We lost 1 day of work. 

LIKE YOU SAY, the autosave didn't work because it quietly stopped saving like the day before. 

I really like collaborating in Team Projects but these saving/syncing issues are a royal pain. 

[Nate Boerman]

I am sorry for your troubles. 

If that is not working, you coulc create another project and copy the contents fo your older project window into the new projec window.  That should allow you to save and continue working in the new project.  Let me know if this works for you.

-Nate

[Kcaudill]

Is there and or will there be a fix for this? This problem continues to happen to our editors accross projects and machines and while my fix usually helps, it's still a major inconvience and then leads to having to consolidate projects.

[Sal154A]

I've been having this same issue too ever since I started using Team Projects 8 months ago. I'm looking at other posts of people having the same issue from over 5 years ago. It's dissapointing that there is still not a fix on a subscription based program.

[martinc1656642]

@Nate Boerman thank you.

I didn't think of that at the moment. I will keep it in mind for next time.

Now, if I do that, how would you merge the two projects together, mine (that I just created with the copied and pasted items) and the one the other collaborator/s continued working on?

[martinc1656642]

And here we go again.
It hasn't been saving for 4 hours, I am glad I saw this now. 
Please, Adobe help us by finding a solution to this. 

@Nate Boerman I copied all of the elements from the Team Project into a new project. I now have to figure out how to merge this into the original Team Project that 2 other editors worked on for the last 4 hours. 

[Kcaudill]

@martinc1656642 This is the worst part, dealing with all of the duplicate assets Premiere will create. We use lots of multicam clips, and Premiere will duplicate every multicam in the sequnece when bringing work back into the Team Project. It really sucks to put more work on the editors (or an AE) but the best way is to then replace clips by timecode (you can re-cut clips in by timecode or option drag) so that the clips in the sequence is referencing the original ones in the Team Project and not all the duplicates Premiere created. It's such a pain to keep things tidy.

[robingroulx]

Hey,

Also having this issue. There has to be a fix for this by now yeah? 

[jaredh58606304]

also having this issue...