Team Project won't save

[robertstonefilm]

For the past 24 hours my team project will not sync with creative cloud. This icon is in the lower left hand corner.

If I try to close the Team Project I get frozen in this window:

If I try to save it as a Premier project I get frozen at this window:

The only way to close down is to force quite but how can I be assured that I won't lose all my work?

This has been happening many times over the past week.

[jmm02003]

This just glitch just happened to me on version 23.1.0 (build 86) just today. Premiere wouldn't save or publish changes to my team project. It also wouldn't let me "save as" locally. Since I read on here that people have lost tons of work due to this bug, I exported all the work I had done as a precaution. I also created a new local project and then copied and pasted all of the sequences + assets from my team project into that new project (since, again, I couldn't use "save as" to save a local copy of the team project). After all that, however, once I hit "quit" the team project published my changes and allowed me to save.   

I think this might have scared me off from Team Projects for the time being, since it felt like I came very close to losing a half day of work over nothing. It's extra concerning that this has been a known issue for over 5 years and that the best trouble shooting guidance from Adobe seems to be "Whoopsy! Just close your project and reopen it... and risk losing hours of work in the process."

[devGuru411]

This problem was minimal and didn't happen often (for me at least) in v2022, however now that we are on v2022.1 (Build 86) the problem seems to have reoccured and is much worse.  Almost every time I save a team project it spins for 20-30 minutes and many times I have to cancel multiple times before it will let me publish my changes.

Come on Adobe - fix this already!

[R Neil Haugen]

It isn't a common problem, as in one expects to have it every once in a while. But it has occasionally happened, and is totally terrifying if you're the one who's had it.

23.1 has a number of posted issues, including program manager Francis Crossman posting on the Premiere forum a warning that Mac users with H.264/HEVC media should revert to 23.0 for now as there are problems with those codecs on Macs in 23.1 as released.

There seem to be a few other things. And it's easy to go back, so I would suggest considering that for now.

Neil

[devGuru411]

Hey Neil,

Actually it's not an easy "go back" because we are using a team project.  To my knowledge once it has converted itself there is no going back unless you literally recreated a new project and dragged everything over from scratch - in which case you would lose all your history as well.  Not a good solution.

[devGuru411]

UPDATE - As of v23.1 (Build 86) it seems there is at least "something" done ... 

My premiere recently crashed earlier today while trying to get updates on a team project.  After I had to force it to close because it wasn't responding, when I reopened premiere I saw the below in my "Recent" list.  As you can see there is now a new "type" of file called "PRPROJ_blah blah" - this appears to be some kind of temporary file that Adobe is creating.  I opened that file instead of my team project and surprisingly my changes were there - whew!

Then, I opened my team project and all my colleagues latest changes (from my get latest pull when it crashed) were actually in the project; it just seems like Adobe locked up after it updated the project for some reason.

Hopefully this will help someone else, it's not fixed but its better than losing an entire day's worth of work.

[devGuru411]

[Paul Erskine 2020]

This worked! I had to look around before I discovered you need to close all projects and go to open a project to see the Recent Files list. The recovered project is not a Team Project, but that's ok. I've been now wanting to pull it out of Team Projects anyway. Not sure how the AE dynamic links will work now, but I'm glad to see my work recovered.

Thanks for posting your solution!

Paul

[Paul Erskine 2020]

By the way, the After Effects dynamic links did not work in the sequence I had exported from Team Projects, so I had to manually re-import each AE comp using File>Adobe Dynamic Link>Import After Effects Composition then replace the comp I had used in my sequence with this newly-linked comp.

I AM NOT HAPPY with my attempt at trying Team Projects for our company. It's currently too buggy for production. I lost a day trying to recover work and if I had been on a tight deadline, I would have smashed my computer to bits in frustration.

For instance, in a Team Project you can drag and drop a AE comp into some sequences, and some not. You try, but the icon turns into a "Nope. No can do". I have no idea why it works for some but not the other. And to make things even more fun, here's an example of a dialog box I got when trying to import an AE comp to my Team Project in Premiere:

That's the entire dialog box. Huh?!

Adobe, this is disappointing especially since this thread full of issues goes back more than 4 years.

Best regards,

Paul

 

[Joe Lining]

10/11/2023 and having the same problem. Pretty sad that Adobe seems to not care about fixing this several year old problem even though they charge us way more money (and recurring, not one time). Starting to see why everyone is switching to DaVinci. Might do it myself.

[R Neil Haugen]

It's a right pain when it doesn't work, no questions there. But the vast majority of TP users aren't having this issue. So we would need some information from you to help solve it.

The OS, some idea of the scope of the project, number of members and such, and probably some screen grabs also. A description of what you're doing ... and what you've tried for trouble shooting also helps.

[devGuru411]

While these are all decent workarounds a "workaround" is not what we need. 
What we need is for ADOBE to FIX the F** PROBLEM!!

We all pay way too much for the software not to work better than it does.  Period.