Workspace fails at the "Connecting to workspace" stage

If your workspaces are failing to launch while displaying the "Connecting to workspace" toast message, we have a few suggested steps to help investigate the issue. 

When you open a ticket with the Support team please provide the workspace support bundle upon ticket creation along with details on how to reproduce the issue - which environment, which type of workspace, etc. 

In addition, here are a few other suggestions to try: 

1. Start up a workspace again, but this time with the Chrome dev tools open:

   1. Monitor the console logging tab for errors, especially related to the query to get the public url

   2. Monitor the network logging tab for calls to get the public url, and results of those queries

      1. The url should be https://deployment.com/u/userName/projectName/notebookPublicUrl/someId

      2. in normal circumstances, it might have a call that 404s because the notebook isn’t ready yet, then a call that succeeds

   3. Capture this output and send to the Support team

2. If you are an admin, capture nucleus-frontend (note there may be more than one k8s pod to look at) main container logs and also the nginx logs while doing #1 – in most cases it should be included in the support bundle, but sometimes the system cannot execute the query

3. Test what happens if you manually put the payload into a browser tab (the payload will just be the url for the notebook like: https://deployment.com/userName/projectName/r/notebookSession/someId/)