Wont let me "Share my Changes"

[alexanderr31337795]

Whenever I try to share changes, It gets stuck at this point in the process. 

[PeterELee]

That's very strange -- it's saying that there are zero changes that need to be shared. Normally the share button is disabled in that case. If you make a trivial change, like creating an empty bin, then try sharing again, does it work?

[alexanderr31337795]

No it does not work after any changes, edits, or time passing.

[PeterELee]

Hmm. If you're willing to share your project data with me (not the media, just the metadata describing the sequences, clips, and history), I'd like to see if I can find out what's gone wrong. I will PM you with details.

In the mean time, I would suggest trying to roll back to a previous auto-save, and see if you can share from there. You can do this from the Media Browser - browse to the Team Project you're seeing this issue with, then click on the Auto-Saves tab. Next, use the slider on the right side to scroll down to an auto-save from before you started seeing this problem. Finally, right-click on the name of the Team Project and choose "Make Auto-Save (...) the latest...". This does not delete any of the auto-saves that came after the one you chose - they are still in the history, but the "current" state will match the auto-save you chose. This may cause sharing to become "unstuck."

[alexanderr31337795]

Okay, how do I share metadata for the entire project. I have found that if I leave it on that screen, it will finally save after about 6 hours. This isn't ideal for workflow.

[PeterELee]

Clearly not! That is not a typical delay. I wonder if you're also experiencing issues connecting to the Cloud. Have you tried logging out-of and back-into Creative Cloud, or uninstalling then re-installing the CC desktop app, as suggested above? Also, does this happen in all Team Projects or only certain ones?

[castleboomer@hpe]

I'm seeing this three and four times a day and it's getting to a point that we are avoiding team projects all together.

Sure would like to see a fix.

[PeterELee]

When you say you're seeing this three or four times per day, does that mean that the share operation eventually completes on its own? What version of Premiere and/or After Effects are you using?

[castleboomer@hpe]

After opening the project I am usually able to share and auto save appears to work until a warning alert appears.  I know I am in trouble when I see the warning icon that says "Collaborators will appear offline because the presence service for "wwtttt2019"(this is the project name) is currently unavailable.  We will continue to retry the connection in the background."  After that sync or trying to close the project ends up with the error  alexanderr31337795​ has show above and after that no activity.  No saving.  No network traffic.  Pretty much a cancel is the only option.  

[PeterELee]

Interesting. Sorry you're having this problem. From your description, that sounds like some sort of network-communication issue. Have you tried logging out of and back into the Creative Cloud application (the one with the icon in the menu bar)? The next level would be to uninstall and re-install the Creative Cloud application (see: How to fix the "Failed to install" error when installing Adobe Creative Cloud desktop app ).

[runklejumblinatorial]

I am having this problem too. Also, I get an auto save error, so I don’t want to quit to revert to the last auto save because I don’t know how much work I’ll lose. Team projects has been such a massive clusterfork the only reason I’m still using it is that I haven’t been able to train our other editors on resolve yet, but I’m working on it.

[PeterELee]

I'm sorry to hear you're having these problems. If you look in the Auto-Save history in the Media Browser, it will show you the time and date of each auto-save, which should give you some idea of how much work might be in jeopardy.

The system will warn you immediately if it detects an error that interfered with auto-saving, but it also monitors the process and will warn you if it has been more than five minutes since the last successful auto-save, even though no errors were detected. This can happen in some cases due to network performance issues, or the need to save a large number of new changes, for example. If you get that warning, the best thing to do is to stop editing until you see that the asterisk next to the Team Project name has gone away, indicating that the auto-save has completed. You can speed up the process by either closing the Team Project or hitting the Share button (even if you then cancel the share operation). Both of these actions bring up a progress dialog and allow auto-save to run much faster. It is not a good idea to continue editing until you have seen an auto-save complete successfully.

Note that the original message is about problems sharing changes. This is distinct from auto-save. Auto-save happens on your local workstation, regardless of whether you are connected to the internet. If you are connected, your latest auto-save is also uploaded to the cloud in the background. Sharing is when you merge your local changes with the shared copy of the Team Project in the cloud.

[runklejumblinatorial]

"If you look in the Auto-Save history in the Media Browser, it will show you the time and date of each auto-save, which should give you some idea of how much work might be in jeopardy"

That's a good tip.  Thanks for that.  But I think we're going to look for a different way to remotely collaborate. Adobe team projects are just too flaky.  Share for autosave, cancel to continue, and exit to revert are all pretty exemplar of the Team Project experience.  That, and like the other guy said, waiting six hours.  Or waiting six hours with a progress window open, then clicking cancel after seeing no progress, and discovering that cancel was the answer all along.  No thanks.

[PeterELee]

I'm sorry you've had such a bad experience with Team Projects. They have been used by customers for several years now, to deliver a number of TV shows, documentaries, and frequently-updated content, so I don't think your experiences are typical. Still, there are obviously shortcomings that are affecting your setup, and those of others here, that we haven't identified or solved yet. We continue to try to fix every issue we encounter, and steadily improve performance.

To be clear about auto-save, it's always running in the background, but it is designed to not slow down the user interface, so it yields frequently. This is rarely a problem. If you have made a large number of changes since the last auto-save, and you're seeing warnings that auto-save hasn't completed in more than 5 minutes, you can effectively say "I'm not going to edit for now -- just finish auto-saving" by closing the Team Project or sharing. This kicks auto-save into a mode where it can use more system resources.

Based on further discussion in this thread, though, it doesn't sound like auto-save performance was the issue here. It sounds more likely to be a network-connectivity issue, or a problem with one of the Creative Cloud services that greatly delayed sharing.

[Peter Sinter]

Same Problem here, has there been a solution. I just created a Team Project on a second Macos Account without admin rights. Even the brand new Project starts up with connectivity issues. I already tried trashing my preferences and disabling the firewall.