Suddenly Unable to retrieve revisions / Unable to retrieve ignored paths

It seems collaborate has stopped working

first I updated my project to 2018 from 5.6. Before I pushed, it all worked fine.
when I transferred via collaborate, the project to my osx machine, it all downloaded but some of the prefabs lost their references.

So i thought I would do a fresh download from collaborate, and then this started happening.
I am unable to list the first error because it only comes up after attempting to download a whole project which takes about an hour.

But i was curious so I logged into the web portal and looked at the assets of the project and then I get this errors

Unable to retrieve ignored paths (-1)

the worst part is that It not just that project. I want to other projects and gave the same error, which has me pretty worried.

I'm really hoping something hasn't gone seriously wrong on the unity servers.

 

Seems you are not alone, I started having this issue about 5 hour ago, and tried everything I could, like creating new project and copying all the asset data to new it and trying to "publish".
Or even upgrading Unity version to 2018.1.5f1 the newest version available in Unity Hub.
But nothing seems to work for now.
So I did the same as you, went to portal and try to check the data in the server and got the same error message.

 

Please accept our apologies for a brief service outage earlier this morning. We had incorrectly deployed using an old certificate for our site that was causing all connections to fail for about 30 minutes. That has been rectified. If you are still having problems, let me know. It should not be failing after 13:00 UTC (2018-06-21).

 

I`m still having the issue.
In the portal and in Collab inside Editor.
Still cannot publish, or either able to retrieve from history.

 

I'm getting the same issue too, my whole team can't publish anything, check on the Unity Services website and get these when attempting to view Timelines or any other tab:

Unable to retrieve ignored paths. (-1)
Unable to export your project. (-1)
Unable to retrieve revisions. (-1)

None of my team members are able to publish anything anymore.

 

Seems it is working for me now.
Portal as in the Editor.
4:55 PM UTC (1:55 AM Friday, Tokyo (GMT+9))

 

Sure enough, we found that some of our non-U.S. regions were also affected. Those have been fixed and things should be operational across all regions, now. Again, apologies for the interruption.

 

This problem again

 

And again.
From the day I started using Collaboration (more than a week), not a day passed it was not working

 

And again

 

Same again

 

Wow, it would be nice if there were some sort of downtime status page for Collaborate..

 

Is there a way to have scheduled downtimes? People are paying for this service and it's standard in the industry to have SLA's.

Or, an error that is more descriptive such as, "Collaborate is down until 16:00 GMT" rather than a generic Cannot submit changes to server

 

[Collab] ExternalAPI::Failure: Authorization token has expired
¯\_(ツ)_/¯

 

Hi @laurentlavigne, this error can happen if for some reason the authorization token for a publish has expired before it could finish. Retrying the publish should succeed, but if it doesn't then please let us know.

 

it happens every day on the laptop, hasn't yet on the desktop

 

How often each day do you run into this error on your laptop? Do they seem to happen during large publishes or publishes of any size? Are there any other Collab operations that seem to cause this error?

 

once or twice a day
even small commits of a few KB (script)
only commits seem to do that

 

Thanks for the extra info. When the commit fails, does retrying them work or do they keep failing?

 

they keep failing for a while and then eventually it goes through