Developer instance release email

[Admin Pro]

This morning (Jan 10 - 2024), I received an email from developer instance support that said:

"Dear Service Now Developer,

Please save your work and release the current instance by the end of next week. The instance has technical issues and must be retired.

Thanks for being an active member of the ServiceNow Developer Program.

Best Regards,
ServiceNow Developer Team"

Is there a way to stop this from happening? In my 8 years plus of having the developer instance, this is my first time setting this message. I have years of configuration on this instance, so XML backup of specific is not an option. I REALLY wish ServiceNow would add a paid tier for developers so we don't have to deal with this nonsense. 

A few questions:

• Is there a way to stop this from happening?
• If not, does anyone know how to get a full backup of the instance so I can later restore on another? 
  • As I mentioned above, XML export is not an option. We are talking several years' worth of configuration.

[Dr Atul G- LNG]

Hi @Admin Pro 

This email is true and SN is taking back the PDI. 

A few questions:

• Is there a way to stop this from happening?  --> NO
• If not, does anyone know how to get a full backup of the instance so I can later restore on another? 
  • As I mentioned above, XML export is not an option. We are talking several years' worth of configuration.

1. In the Application Navigator, go to Connections & Credentials > Credentials
2. Click the New button in the upper right-hand corner
3. It will ask "What type of Credentials would you like to create?" - select Basic Auth Credentials
4. Fill in "Name" with how you want to identify your Credential
5. Fill in "Order" with its intended order of attempt if multiple Credentials exist (though this is not used in source control, so any number will do)
6. Fill in "User name" with the username used to authenticate the source control repo
7. Fill in "Password" with the password used to authenticate the source control repo. If you're using Github or a repo that requires multi-factor authentication, use a personal access token instead.
8. Check the "Active" box to make this Credential usable
9. Click the Submit button
10. Copy the URL to your repository
11. Open Studio from the Application Navigator
12. From the navigation bar at the top, click Source Control > Link to Source Control
13. Fill in "URL" with your repo's URL
14. Fill in "Credential" with the one you just created
15. Click Link to Source Control

https://developer.servicenow.com/dev.do#!/learn/learning-plans/vancouver/new_to_servicenow/app_store...

https://docs.github.com/en/enterprise-server@3.9/authentication/keeping-your-account-and-data-secure...

[Mark Roethof]

Hi there,

We all feel your pain. And it is as Atul already mentioned.

You are also not unique in this. This has been mentioned by hundreds of people (or perhaps even more) in the past few weeks, all dealing with the same or even worse... PDI suddenly gone, no notice at all.

What the reason is behind this? No clue, no one has mentioned the reason yet. Also as an MVP, I haven't heard anything.