Collaborators not loading

[Maximilian255338098zlx]

Hi,

I am running a Teams Project, all Team Members (3) are on 23.1

While I (project owner) see, whenever collaborators are online, my colleague does not "see" any collaborators, and receives an error message when clicking on the collaborators icons.

There was a problem loading collaborators for this Team Project. Please try again later.

This results in squence-lock not happening (I assume because my collaborators project thinks noone else is working) and various sync problems (duplicate sequences etc.)

As I understand from reading in this forum, Teams Projects in 23.1 are not reliable currently.

Is it safe to install 23.0 and open the current Teams Project there?

Thanks!

Max

[Nate Boerman]

Hi there,

Sorry for the poor experience.  It sounds like there was an outage in one of our subservices.  Are you still experiencing this issue? 

-Nathan

[Travis23137878xtk7]

Yes I am, exactly the same

[Maximilian255338098zlx]

Hi, sorry for the late reply.

We had to change our workflow and switched to editing on one machine only (it was a planned step in the project timeline anyways, we took that step earlier than planned).

But as from what I had seen in between (starting the project once from another machine), the "non owner" user could still not be seen. 

I will give this another test.

Thanks, 
Max

[Nate Boerman]

Hey Max,

Would is be possible if you could reproduce this issue and send me the logs for  the event  they should be found  in 

Win - C:\Users\nboerman\AppData\Roaming\Adobe\Team Projects Local Hub\2.0\logs
Mac - /Users/nboerman/Library/Preferences/Adobe/Team Projects Local Hub/2.0/logs

For the owner and non-owner?

-Nate

[Aditya256042302ti0]

Our whole team is experiencing this issue. It begins when we find out one of our team member is kicked out randomly and when we try to go in to add them back in, this first error pops up:

There was a problem loading collaborators for this Team Project. Please try again later.

After we close that dialogue box, all the collaborators in the teams window have dissappeared and when we try to add them back, a new error pops up saying

Failed to send invitation to "Team Member Name".

This project now has become useless as a team project and we have to create a totaly new team project and add the media from the previous one and re-invite all the collaborators. This has been extremely frustrating for us dealing with up to sometimes 8 new versions for a single project. Everyone is on Premiere 23.2, Mac OS Ventura 13.2.1 and have all cleared caches. Has anybody figured this out?

[Nate Boerman]

Hey Aditya

Would is be possible if you could reproduce this "Failed to send invitation to "Team Member Name" issue and send me the logs for  the event  they should be found in 

Win - C:\Users\nboerman\AppData\Roaming\Adobe\Team Projects Local Hub\2.0\logs
Mac - /Users/nboerman/Library/Preferences/Adobe/Team Projects Local Hub/2.0/logs

-Nate

[DA Hegarty]

Yes we've been having the same problem for more than a week. 3 users (1x owner & 2x collaborators) all running PP 23.1. Owner and 1 collaborator (both on non-Apple Silicon Macs) could see collaborators but the collaborator on a new MacStudio could not see anyone, whether online or offline. This creates multiple conflicting sequences every time changes are Updated/Published even if those sequences are only viewed and no changes are made in the sequence.

Everyone upgraded to PP 23.2 and now the issue is worse, no one can see anyone else.

It's costing us so many editing person-hours and euros at this stage, v. frustrating and expensive.

[Nate Boerman]

Hey DA,

Would is be possible if you could reproduce thiw issue and send me the logs for  the event  they should be found  in 

Win - C:\Users\nboerman\AppData\Roaming\Adobe\Team Projects Local Hub\2.0\logs
Mac - /Users/nboerman/Library/Preferences/Adobe/Team Projects Local Hub/2.0/logs

For the owner and the two collaborators?

-Nate

[DA Hegarty]

Just DM'ed you a link to the log file

[Udo_Pawlik]

We identified a server-side bug that caused the invitation issue. A fix has been deployed, can you check if the issue now resolved on your end?

Best,
Udo