Takes too long for the doc management service to activate in a new BIM 360 project via Forge API

[Anonymous]

The doc management service takes too long to activate. We are experiencing this issue since last Friday. 

Projects get created without problem, and users get added to projects(even-though they do not get an invitation email until doc management services are active). However, the doc management services keep spinning between 1 to 4 hours  so, we do not have access to project folders. I found others having the same issue in Stackoverflow. 

https://stackoverflow.com/questions/59570209/is-it-possible-to-load-new-cloud-bim-360-links-in-a-rev...

https://stackoverflow.com/questions/63691307/the-document-management-is-not-active-from-forge-api

[zhong_wu]

There was an issue related to user token, and this was fixed around early this week, did you still see this issue now?

[zhong_wu]

Hi, there was an issue related to user's token, not sure if this is caused by that regression, but this was fixed early this week, did you still see the issue now?

[adt]

It was pretty slow yesterday morning and the day before, but did eventually resolve itself later in the day.  We will continue to monitor.  I did see on the health website yesterday that there was downgraded services so it could have been tied to that.  Thanks for the quick reply!

[mcorredor]

We are also having some issues with this. "Activating..." and the loading wheel have been loading for a long time for Document Management, Project Management, Design Collaboration, and Model Coordination. 

[jackchaskell]

I'm also experiencing this still, has there been any resolution? My project services sit and spin for a ridiculous amount of time when activated through the API.

[zhong_wu]

Are you saying the Docs module is always in activating mode with spin? Can you add a project admin to the project to see if that solves the issue? 

[jackchaskell]

It continues to hang even when a project admin has been added. I have found that sending a PATCH projects request to toggle the project status to "inactive" and back to "active" seems to activate the services - so I at least have a workaround.