Skip to main content
Participant
Nov 4, 2026 9:17 AM UTC
Investigating

team project sync is stuck

Hi,

 

We have a large Team Project that stopped syncing on one editor's Mac (Germany). It still works normally on our Windows machine (Israel). Customer care chat only gave generic steps, so I'm hoping someone from the Team Projects team can look at this. The Local Hub logs point to a server-side problem.

 

Setup:

- Premiere Pro 26.5.2 on macOS (it fails the same way on 26.5.1)

- Production ID: 8661a1d4-35fd-7471-14dc-a7bafa498f30

- Remote session: 8661a1d4-35fd-7471-14dc-a7bafa498f30*b6344868-cd27-d0dc-9c8f-87adc69ef934

- Region: an1 (cc-api-teamprojects-an1.adobe.io)

- About 11,000 media locators in the project

 

What the logs show:

 

1. The bulk download never finishes. Every pull fails on the same request: .../productions/8661a1d4-...*b6344868-.../<revision>/bulk/get

Each attempt is cut off at almost exactly 60 seconds, with HTTP 504 "upstream request timeout" or NSURLError -1005 ("connection lost"). After 11 retries it logs "Bulk Enclosure Get failed" and rolls back. Data starts streaming before the cut, so the response looks too big to finish within the 60s gateway timeout. This has happened since Oct 26, on revisions 5eecf7e6..., ad2a0c7e... and 4b676a4d…

Example request IDs (UTC):

- 961e910a-ecff-479e-bc39-10e78d15dbce: 2026-11-02 16:21, HTTP 504

- 02c5289e-fc8c-4513-84c9-eadcb53ebcfe: 2026-11-02 16:34

- 9fffc579-a3cb-43df-ace0-50e86d5bb253: 2026-11-04 05:39, ad2a0c7e.../bulk/get

 

2. With a fresh Local Hub, the project can't open at all. It ends with "Synchronization Failure - could not be synchronized due to a network error", because it needs that same bulk download.

 

3. With the old Local Hub restored, the project opens, but the session is stuck. The local base is remote revision 5eecf7e6, and remote HEAD is ad2a0c7e. The log shows "EngageSessionConflictState" and "cannot automatically resolve remote and local differences", and every pull (RemoteDiffDuplicator) and push (LocalDiffDuplicator) fails immediately with -1606090343 and "session HEAD does not match transaction required HEAD". "Get latest changes" just sits on "Waiting for Team Project to synchronize...". The editor's new work can't be shared. On Nov 3 and 4 local changes were also discarded three times while trying to recover.

 

What we've tried: restarts, other networks, a VPN, signing out of and back into CC, clearing the media cache, moving and resetting the Local Hub (this makes it worse), a clean reinstall, and switching between 26.5.1 and 26.5.2.

 

Questions:

- Can the bulk/get for this production be allowed to complete, for example with a longer timeout or smaller chunks? Can the production be moved to an EU region? The editor is in Germany and the project is hosted in an1 (Tokyo).

- How do we safely get this Mac out of the conflict state without losing the editor's unshared local changes?

 

Sanitized Local Hub logs are attached (user name and tokens removed). Thanks!

6 replies

Participant
Nov 5, 2026 8:28 AM UTC

Thanks for reaching out! 
The OS is macOSTahoe V 26.3.1(a)
and the CPU/GPU is  Apple M1 Chip

Translate
R Neil Haugen
Legend
Nov 4, 2026 5:18 PM UTC

 For a number of years, a colleague and I were the most helpful users on this forum and the separate Team Project forum for TP issues. By the way on the TP forum, the staffers are normally very helpful very quickly. I think that forum is still operating and it’s better to post TP questions ‘over there’ as the TP staff answers right away.

Mo and I gave presentations to other Adobe Community Professional members on this, and worked directly with the TP staff on testing and practical use. So … for years I was pretty “grounded” in TP use.

BUT … when they came out with the Productions mode for collaborative workflows, Mo and I tested that. And then we were contacted by LucidLink to see if we wanted to help them test their at-the-time yet unreleased product in concert with Adobe staffers. We jumped at it.

And shortly after, Mo and I discontinued all use of Team Projects. Productions was vastly easier to stay up with, and although not perfect, as you still cannot track usage across the projects of a Production, the capabilities outweighed the disadvantages. 

Mo and I moved totally to Productions, and I’ve not touched TP except for a couple quick tests for other users now in probably five years.

I’m in Oregon, Mo in Cape Town, nearly opposite spots on the planet. He calls me on WhatsApp to say he’s uploading a folder of files of his incredible AE work, to our shared workspace on Amazon S3 servers in London.

While talking I go to my ‘virtual drive’ which LucidLink creates, and your local machine ‘sees’ as a local drive … and watch the folder pop up. Then files start popping up in the folder, while we are still talking..

As soon as I see individual files, I can go into Premiere and import those files from the virtual drive … which files do NOT exist on my machine! … and even drag to a sequence and start playback.

And the folder hasn’t finished uploading to London from Cape Town yet! It’s full-on Harry Potter magic but works amazingly well. IF you have above 450Mpbs low-latency up and down of course. We’re both around 980Mbps now so it’s really slick.

Note … I’m using his files, which “live” in London now, in our shared Production, which also can live in London. Working on my machine. And I’m all PC, he’s never touched anything not Mac in his life.

 

You might consider the transition to Productions. They’ve maybe updated some of the links I’m posting. And ALL Karl Soule’s YouTube vids on Productions for Adobe are quite good and well worth the time.

 

Premiere Pro Productions Introduction

Using Productions in Premiere Pro

Adobe Long-form and Episodic Best Practices Guide 

 

Jarle’s blog expansion of the pdf Multicam section: Premiere Pro Multicam

Translate
Everyone's mileage always varies ...
Amy the Stuv
Community Manager
Community Manager
Nov 4, 2026 4:51 PM UTC

Hello ​@Omer26291846ol48 

Welcome to the Premiere Forums. Could you let us know what Mac OS that system is running, and what Chip or GPU / CPU combination it has? Is everyone on the same version of Premiere and Creative Cloud?

I will take these logs and reach out internally to see if there are any other ideas to try. Apologies for the inconvenience.

I would highly suggest the editor on the Mac save a project externally outside of Teams as a backup. 

  • Edit -> Team Project -> Convert Team Project to Project... will create a new standalone Premiere project (prproj) as a snapshot of the Team Project, leaving the existing Team Project untouched.

Best,

Amy

Translate
Participant
Nov 5, 2026 8:29 AM UTC

.

Translate
Participant
Nov 5, 2026 8:29 AM UTC

Thanks for reaching out! 
The OS is macOSTahoe V 26.3.1(a)
and the CPU/GPU is  Apple M1 Chip

Translate