Skip to main content
M
megs35119035
Participating Frequently
May 17, 2021
Question

Teams Project Auto Save Error

  • May 17, 2021
  • 3 replies
  • 2704 views

My team is working remotely and using Team Projects to edit in Premiere. One of my editors shared that in various Team Projects, she kept getting auto save errors: "There was an error auto-saving the changes you have made in the last XX second(s) to the Team Project....Your changes cannot be saved while the problem persists. Please close and reopen the Team Project to revert to the last auto-saved version."

This held her up for most of the afternoon, as she was unable to share any changes. I had her log out of Adobe on her machine and reboot, log back in, and try again...to no avail. Any insight here? I seem to be ok in the project, but I did have one other editor in addition to this one mention auto save errors. Thanks!

This topic has been closed for replies.

3 replies

P
pls help omg
Participant
May 19, 2021

we get this.. a lot.. 

 

W
Walon5FF1
Participant
August 4, 2021

Hi! We ran into the same issue. Did you guys find a solution? Or you just say goodbye to Team Project. This issue really annoyed us a lot!!!

U
Adobe Employee
Udo_Pawlik
Adobe Employee
May 18, 2021

Hi, 
Usually, auto-saves are nearly instantaneous, but we've seen some cases where they can take many minutes to complete (with several subsequent auto-save errors).

The most common culprits are:

  1. Changes that touch several thousand assets at once. This can include importing many assets in one go or converting a large standalone project to a Team Project.
  2. A slow drive in the system

 

If she ignores the error dialog(s) and continues to wait, it's likely that the auto-save operation will complete eventually, and that subsequent auto-saves will be faster. It's hard to predict how long it will take to complete.

Can you also provide a bit more information:

  • How many total assets are in your team project?
  • Is the media on a external drive?
  • Which version of Premiere Pro are you using?

Best,
Udo


Udo Pawlik  |  Sr Software Product Quality Specialist |  Adobe  |  p. 408.536.3410  |  upawlik@adobe.com

 

    M
    megs35119035Author
    Participating Frequently
    May 18, 2021

    Hi Udo,

     

    Thanks for your response. Our Team Project is very small, maybe has only about 150-200 assets tops. Our whole team is using Premiere Pro v 15.2 (the latest update). I believe she has downloaded the assets she needs onto her external hard drive to work--so a slow drive on her end might be the issue. I can get specific specs on that later today. Thanks again for your insights and help!

    -Meg

    M
    megs35119035Author
    Participating Frequently
    May 19, 2021

    Hi again,

    So it looks like my editor hasn't been using an external hard drive for her media assets (it's a small project, so something she didn't think she needed for the time being). However, she's been working on this for several months without any autosave issues. She'll be getting an external hard drive to work from soon, but I'm just curious is there are any other suggestions/insights into this problem. Even I have been having occasional issues with auto save, and I know my external SSD and computer RAM are up to snuff. Thanks!

      R Neil Haugen
      R Neil Haugen
      Legend
      May 17, 2021

      Did she successfully get to an older version of the project on her machine, so the project was fully functional?

       

      If she didn't, does she know how to find the Team Projects saved versions?

       

      Edit/Team Projects/Browse AutoSaves is listed in the manual, as well as in the Creative Cloud app has a section for listing auto-saves for a TP project file. Or the Media Browser panel, on the left they show going to the Creative Cloud folder and the Team Projects Autosaves subfolder, then selecting a save from the list.

       

      Neil

       

       

       

       

      Everyone's mileage always varies ...
        M
        megs35119035Author
        Participating Frequently
        May 18, 2021

        Yes, thankfully she had a backup saved. Unfortunately, when she goes back to an older version of the project, she continuously gets change resolve issues (seems to be a weird sequence messing with everyone)--that I've deleted. Whenever she goes to share her changes though, it brings that sequence back. Something else going on entirely aside from the autosave issue, I realize. I made an entirely new version of the project, shared it via Teams, and the autosave issue still happens for her.

        Terms & ConditionsAccessibility statement
        Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices