Possible restrictions on Google Cloud API configurations.

While performing aggregate's release testing I encountered an issue which I believe is connected to some restriction when generating API configuration on Google Cloud service. I was able to open and use maps on both tomcat instance a GAE with a configuration which I generated a while ago, probably more than few months. I was able to use them parallelly at the same time, on 2 different browsers windows. I generated a new API conf from a different Google account, I use it for GAE instance and it worked just fine, but when I use those new configurations to some other instances - I had a developer map version only on all instances with the same API conf (3 instances)- so results were not that good. I changed again API conf for 2 of them and left a new configuration for only one GAE instance. After refreshing, I still saw a developer map version. When I checked again after like an hour I saw a normal Google map.
By developer map version I understand:

I assume that it is possible that Google added some new restrictions about API configuration and they can be used only on the one instance at the same time. I am wondering if anybody has the same conclusions or observations as I have. If somebody could confirm that it would be good to inform users about that.
cc @yanokwa @lognaturel and @ggalmazor

Start by reviewing the reported behavior and checking whether Google Cloud API configurations can produce different map versions across multiple Tomcat and GAE instances. Consult the Sphinx documentation and verify the behavior with the old and newly generated configurations; done means confirming the restriction and documenting it for users, or recording that it cannot be reproduced.

Written by the indexing model from the issue text.