Sorry to hear this! A few questions:   Are you seeing the same error code (-1609629695)? Have you noticed if the error comes after adding a particular clip or effect (e.g. a MoGrT or AE comp)? Does your Team Project contain both After Effects compositions and Premiere Pro sequences? Is your project partner running the same versions of Premiere and After Effects? ... View more

Can you provide a little more detail about this metadata? Specifically, what sort of metadata is it, and how is it being attached to a sequence? ... View more

I'm afraid I don't know After Effects that deeply, beyond the parts that integrate with Team Projects. I'm asking around, though, and I'll let you know if I get any good suggestions. Do you have a preference set to make AE open the last project when it launches? If so, there may be a problem with that specific project file. One way to work around that would be to reset your AE preferences by holding down Command+Option+Shift when launching AE (Ctrl+Option+Shift on Windows): Setting preferences in After Effects. You could also try launching with Caps Lock enabled, in case the error is being triggered by rendering. ... View more

The original question was about this error being reported in Team Projects. To the best of my knowledge, the Team Projects bug in question was fixed in AE 16.1.2 (the latest version). It sounds like you are seeing this error message with a standalone project file (.aep), though. Is that the case? If so, there's going to be a different underlying cause, possibly a damaged .aep file, and I suggest trying the After Effects forum, or contacting Adobe Tech Support directly. ... View more

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. ... View more

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? ... View more

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. ... View more

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 ). ... View more

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? ... View more

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." ... View more

Team Projects don't do any additional licensing checks, but unexpected things can sometimes happen if you have the same Team Project open at the same time as the same user on multiple systems. Team Projects rely on Adobe IDs to resolve any conflicts, so multiple changes coming in from the same Adobe ID can lead to unexpected results. Do you leave the same Team Project open on all of these systems, or do you close it when you switch between them? Also, can what version of Creative Cloud are you using, and what auto-save error(s) are you seeing? The original post was for an error code that is no longer reported in the current version of Creative Cloud. ... View more

Linked Team Projects only work in Premiere at the moment (the links are ignored by AE, which does not currently support having multiple projects open at once). If your Team Project has a large amount of media, or many AE comps, or many Pr sequences, then you may be better off creating separate Team Projects for use in AE and Pr. Put your comps and the media they need in the AE Team Project, and put your sequences and the bulk of the media in the Pr Team Project. Render your comps in AE, and import the rendered media into the Pr Team Project. This will likely reduce your load times significantly in both AE and Pr. ... View more

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? ... View more

Normally, any AE comps should be skipped when you convert a Team Project to a .prproj in Premiere (you would need to open the same Team Project in AE and export as a .aep to create standalone versions of any comps). My best guess is that the comps in the standalone prproj are, in fact, links to the original Team Project. There's no mechanism that I know of for Premiere to create .aep files when converting a Team Project to a .prproj. ... View more

As Jawattndatt​ mentioned, we believe we have identified the underlying problem and are working on a fix. Given how long your project takes to open, it might help to split it into a few pieces. For example, create a separate Team Project for each of your top-level footage bins, and consider using a couple of separate Team Projects for logically-distinct parts of your program, if that makes sense (one per reel, or episode, etc.). Smaller Team Projects generally load and auto-save more quickly than larger ones, and the difference is larger than the number of items alone. You can also avoid opening projects you won't need on a given day. You can create a master Team Project with links to all of the sub-projects to help keep things organized (Create a Team Project ). ... View more

Sorry to hear you are experiencing this as well. A fix will be in the next AE maintenance release, coming soon. In the meantime, I will DM you instructions (which involve setting debug flags). ... View more

I have DM'ed for more information. Yours and the previous forum posts are the only two reports I know of regarding this issue. It would be great to get more information so we can track it down. ... View more

That's strange. Are the AfterEffects comps coming online in Premiere on the older machine? If the slowdown is, indeed, DynamicLink, then not having AE installed, or having a version that's not compatible with your version of Premiere would cause the Team Project to quickly give up instead of making those costly DynamicLink connections. Of course all of the comps would be offline in Premiere. If the comps aren't the issue, then it's hard to say what it might be. Did you check %APPDATA%\Adobe\Common to see if the uninstaller cleared out Media Cache, Media Cache Files, and Team Projects Cache? If not, try deleting those, and renaming Team Projects Local Hub (that one contains your auto-saves). ... View more

I'm sorry to hear you are also running into problems. The original issue didn't involve a crash, though, so this might be something different. If possible, can you DM me your crash logs? As a temporary workaround, you should be able to roll back to a previous version of the Team Project, before it was edited in a newer version of AE: 1. In the version of AE that was working, do not open the Team Project directly. Instead, using the default AE project, or any standalone AE project, open the Media Browser and find the Team Project you want to roll back. 2. Click on the "Auto-Saves" tab for that Team Project in the Media Browser, and use the slider on the right to find an auto-save that was not opened in the new version of AE. 3. With that older auto-save in view, right click on the Team Project name in the left side of the Media Browser and choose "Make auto-save (xxx) the latest...". When you next open the Team Project, it should be restored to that earlier state that does not contain any incompatible data. ... View more

I have not seen that problem before. It's especially odd that closing and re-opening the project would produce different results. I will reach out via DM to see if we can gather any additional data about what might be triggering the issue. ... View more

Based on your description, this sounds like a different issue that what's been discussed in the rest of this thread. Is it possible that more than one person is logged in with the same Creative Cloud login ID at the same time and has the same Team Project open? That can cause some unexpected issues similar to what you're describing. If not, what sort of storage are you using? Is it possible that drives are coming on and off line? One of the ways that Team Projects are different from standalone projects is that Team Project periodically scan all mounted volumes looking for media that matches what's in your open Team Projects. If something about your setup confused that scanning logic, that might potentially cause media to go temporarily offline, then come back online once it rediscovered the media files. For example, if there were copies of the same media on two drives, and one of them became disconnected. It would normally discover and link to the duplicate media in less than 5-10 minutes, though. ... View more

I haven't seen this problem before, but can you verify that your preview files are set to render to the same location for both your project and your Team Project? In a Team Project, the scratch disk settings are under File/Team Project Settings.... In a standalone project, they are under File/Project Settings/Scratch Disks.... If the standalone scratch disk setting is set to "Same as Project", that is likely to cause an issue for Team Projects, since the project location and structure are completely different than in standalone projects. ... View more

That's interesting. Is this a third-party effect? If it is updating its internal data every time you move the time bar, for example, that would result in many edits to the sequence or comps that filter was used in. I'll reach out to you via DM for more info. ... View more

Can you spot any pattern in which assets, or types of assets are getting marked as edited? Also, is there any chance that two or more people are logged in using the same Creative Cloud ID? If different people make changes to a Team Project using the same Creative Cloud ID, it can cause all sorts of unexpected changes, because changes made under one CC ID will be silently synced to any other system that's logged in with the same ID. Also, which applications are you using with your Team Project? Premiere Pro, AE, AME, Prelude, or some combination? ... View more

Are you both making changes to the same sequence? If so, I would recommend splitting your work into multiple sequences, if possible. If you put all of your sub-sequences into a master sequence via nesting, then there should be no conflicts when you edit different sub-sequences. If the conflicts are on media files, and you're using proxies, we have seen some cases where sharing changes before proxies have finished rendering could lead to footage being marked as edited when the proxies came online. ... View more

I'm sorry to hear that you're running into this issue. Can you try the following? 1. Launch Premiere Pro 2. Create a new project (can be either a standalone project or a Team Project -- it's temporary) 3. In the Media Browser, browse to the Team Project that's having trouble auto-saving (it should be under "Creative Cloud/Team Projects Versions") 4. Right-click on the Team Project and choose "Make New Team Project from Version..." 5. Open the copied Team Project and see if it auto-saves new changes successfully. If you have a lot of unshared changes, you can also create a new Team Project from an Auto-Save instead of a shared version. To do that, switch to the "Auto-Saves" tab in step 4 and choose "New Team Project from Auto-Save..." when right-clicking the Team Project name. The next Creative Cloud release will contain a fix that should hopefully make these workarounds unnecessary. ... View more

Precisely. The master project effectively becomes a directory to let you easily find the other components. ... View more