Adding a second graph to a database seems to cause a connection issue

[BillmanH]

I have some scripts that have been connecting to Azure's CMDB Gremlin Graph (systems) for some time with no problem. Using a generic g.V().count() to verify.

Basically:

client.submitAsync("g.V().count()")

This runs fine when connecting to the first graph. However, I have added a second graph to the same db graphdb called stagingsystems and it won't connect.

Both of the two graphs are in the same location, same instance, and in the same graphdb. So the only thing that I'm changing should be "username" which is a link to the path of the graph.
from: username = '/dbs/graphdb/colls/systems'
to: username = '/dbs/graphdb/colls/stagingsystems'

The endpoint and the key should be the same. Data from systems not from stagingsystems. Checked the spelling.

• Both graphs have at least one node in them.
• Both are in the same resource group, same cosmosdb instance

Is there something that changes when you add a second graph? It would be tedious to add a whole new instance just for this extra graph. I feel like it should be possible to access that second graph and that the graph username should have the same format.

Am I missing something?