It may happen that an analysis of modules containing a very large dependency tree (>2000 elements) causes the session to fail during an analysis. This will impact only the particular session, not the complete instance. Due to sticky sessions the user in this case may experience a 504.
To resolve, you must get rid of your session. You might try to get a logout managed. It might be difficult as you will be redirected to the broken session. So either try using a private browser window or remove your TrustSource cookie and login again.
We have learned from this event and are about to develop several solutions to prevent further appearances. However, the amount of incidents seems to be rare (as might be the case of having so many dependencies in one component). Probably you should think of using such components as “infrastructure components” instead of module dependencies. see our knowledge base for more information on infrastructure components.