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 

The image shows the error on my dev instance panel, is there really no support for Dev intances?

Atul: No Support available
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.

Atul: Losing and gaining / new instance is part and parcel of this joruney.

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. Atul: Wait for some time, if it not wake up , consider it dead and release this.
8. Despite me having lost or released Instance A two times, when I get a new instance I will get A back along with B.
9. Atul: No, every time you request , you get a new instance.
10. 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?

Atul: No support of PDI 😞 

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

[lewismac]

@Dr Atul G- LNG 
I have released my instance and requested a new one 2 times now.
Every time I request a new one, I get the same one back AND a new, different one.

When I click on 'Start Building' , after requesting a new instance, It links me to my previous instance - SSO is still active. MID Severs are still running.

Additionally, my Dev website states I am on Vancouver.. (it never 'wakes')

But My instance... Utah - instance Dev166161

Statistics for: Demo Server @ dev166161.service-now.com:80 at: Thu Nov 16 12:00:29 PST 2023 (Refresh)
Connected to cluster node: app128036.ytz3.service-now.com:dev166161002
Build name: Utah
Build date: 06-23-2023_2224
Build tag: glide-utah-12-21-2022__patch4-hotfix2-06-23-2023
Instance name: dev166161
Instance ID: 044d7aabdb69a19891232f17d4961960
Node ID: a2989b87959cd41c846eea3a768ac5f0
Instance State: ONLINE
IP address: 10.87.128.36
MID buildstamp: utah-12-21-2022__patch4-hotfix2-06-23-2023_06-23-2023_2224

Then a few days later, I get 'Inactivity' emails for a new, different instance I never connected to Dev117724:

[Dr Atul G- LNG]

Hi @lewismac 

Greetings!

It is very very rare you get the same PDI again when you request for new PDI. Seems something wrong with infra :(. If you are confused/in doubt, do one thing, release the PDI

The email you got , indicates, if you not use your PDI, it wll taken back.

[lewismac]

@Dr Atul G- LNG  Do you even read the comments when you provide answers?

I ALREADY TRIED RELEASING THE INSTANCE 2 TIMES PREVIOUSLY, AND IT DID NOT HELP THE ISSUE

WHEN I REQUEST A NEW INSTANCE, THE PROBLEM IS THE SAME.

I told you this here:

And here: