Error with Developer Instance - Cannot wake, 'Report' does nothing, multiple instance is associated.

[lewismac]

The image shows the error on my dev instance panel, is there really no support for Dev intances?
Amazingly I have 2 instances (Lets call them A and B).
I have been using Instance A for months, but while instances were down a few months ago, I 'lost' this instance and had to request a new one. This gave me a new instance... which I also lost.. and now I have B.

These are the issues I have identified:

1. Developer Website is states I am associated with instance A (The 'Start Building' button that launches the instances goes to A).
2. Warning emails for inactivity, state that instance B is the instance that has been inactive.
3. Developer Website states the instance (A?) is hibernating.
4. Instance A is online - I am using it even today as I am writing this post.
   My MID Servers and ACCs are connected to this instance, and have been for months.
5. Instance B is hibernating.
6. Developer Website cannot: Refresh or wake Instance B from hibernation.
7. Despite me having lost or released Instance A two times, when I get a new instance I will get A back along with B.
8. I am unable to Wake, or log into B, so I am destined to reach the inactiity time out.
   This happened before so I expect it will happen again.

I am very happy to keep instance A (it has all of my development for months with many clients), but I have no control over the inactivity of B and it appears that it will eventually take A offline, like it did before.

This is clearly a bug with the dev instances and appears to be linked to my account, is there really no support for this?

The only fix I can think of is abandoning my ServiceNow account - but what about my learning, certs, etc?

[Dr Atul G- LNG]

Hi @lewismac 

Seems it is some technical issue and unfortunate there is no support available on PDI.

[lewismac]

@Dr Atul G- LNG, any response for my follow up comment?
When I release, then request a new instance, it does not fix my issue. Read more about this above.

[lewismac]

@Dr Atul G- LNG  Check this out -
I released my instance, I now need to request a new one.

So I request a Vancouver one:

The instance was instantly available (vancouver):

Notice when I click start building ... I go to instance Dev166161 - Again! Look at the URL
The admin password is wrong, which is not normal for a freshly requested instance!
AND MY SSO IS STILL ACTIVE! You see the log in with microsoft button?