Lily Li
ServiceNow Employee

This blog is being updated with the latest info. Please see information with a * next to it as newly updated information. 

Please also subscribe to this blog post by clicking the drop down arrow to the right and clicking "subscribe".

 

*2/8/24 Update:

 

We are currently optimizing the hardware in the new data center.

 

As a result, PDIs within the old data center will not be reclaimed until the new data center is fully optimized. While we encourage users to back up their data with source control regularly, those who have not lost their PDIs will retain them until further notice.

 

PDI Best Practices

 

Keep in mind that PDIs are intended for short-term use, serving as sandboxes for experimentation. They do not offer the same level of support as paid-for ServiceNow instances. Think of them as display phones in a cell-phone store: useful for exploring the interface and testing new apps and features, but not suitable for storing personal or critical information.

 

Therefore, it's essential to regularly back up your data with source control. This ensures that in the event of any PDI issues, you can easily retrieve your data.

 

We will continue to keep you updated throughout this process. If there are any questions or concerns, please leave a comment and we will do our best to give you a timely and thorough response.

 

--------------------------------------------------------------------------------------------------------

 

To our esteemed developers, 

 

We've got some news we’d like to share about our Personal Developer Instances (PDIs).  

 

As some of you know, there have been unexpected scares within the PDI space in the past couple of weeks. We understand this is a serious matter, and we want to be transparent about what went down, why it happened, and extend our apologies.  

 

If you are looking for instructions on what to do next, scroll to the bottom of this post for any information you may need. 

 

The What: PDI Infrastructure Migration 

 

Recently, many members of our Community received emails informing them that their PDIs were being promptly retired. This is because we are migrating our PDI infrastructure from one data center to another. The entire migration is a result of our continued mission to elevate your PDI experience and further enhance security.  

 

The Why: Enhancing Data Security 

 

Our commitment to enhancing data security led us to this decision. The new data center includes enhanced safeguards, ensuring a more secure environment for the data within your PDIs. However, ServiceNow needs to retire instances in the old data center to make this upgrade happen. Those who want to continue their PDI journey need to request a new instance. 

 

Our Apology 

 

We know this migration has caused disruptions and inconveniences for many members of our developer space. Some of you have lost work, and, at the bare minimum, losing access to your PDIs and having to resubmit for a new one is far from an ideal scenario. We acknowledge any frustration or challenges this may have introduced and want to assure you that we value your feedback. We are committed to improving our communication processes and actively engage in regular discussions with our engineering team to ensure a smoother and more transparent transition in the future. Your experience matters, and we appreciate your patience and understanding as we work through these improvements together. 

 

What's Next: Instructions for how to proceed. 

 

As always, if you have a PDI, please ensure that you are consistently backing up your work with source control. If you currently have a PDI within the old data center, this is especially the case.

 

FAQs

What happens if I open a PDI and it goes to the old data center?

  • We are currently optimizing the hardware in the new data center. As a result, PDIs within the old data center will not be reclaimed until the new data center is fully optimized. While we encourage users to back up their data with source control regularly, those who have not lost their PDIs will retain them until further notice. If you open a PDI and it is in the old data center, please regularly back up your data with source control.

How will I know if my PDI is already in the new data center? 

  • The best way to know if you have a PDI in the new datacenter is to look at stats.do. 
    • Login to your instance. In your Filter navigator type “stats.do” and press enter.LilyLi_0-1705961140296.png 

LilyLi_1-1705961140301.png

  • Look at line 2 in the above image: 
    “Connected to cluster node: app128179.ord191.service-now.com:dev202179001” 
  • If this line contains ord191 or aus191, your PDI is in the new data center.  
  • If this line does not contain the above phrases, your PDI will be retired shortly after February 1st.  

How can I export or back up my data?  

Where do I go to get a new PDI?  

  • Once your PDI has been released, you may log back in to https://developer.servicenow.com, and press "Request Instance". Follow the instructions to gain access to your new PDI. 

 

We appreciate your patience, understanding, and commitment to innovation within our Developer Community. We promise to learn from this experience and are working hard to ensure smooth transitions moving forward.  

 

Best, 

The ServiceNow Community Team 

52 Comments
paulmorris
Giga Sage

Regarding the following:


@Lily Li wrote:

When can I expect to lose access to my current PDI?  

  • If you have not yet lost access to your PDI, your current PDI will be released from your account in early February, at which point you can request a new one. You also can request a new PDI beforehand.  

 


I have already done this, but the new PDI was still in the old DC, which was followed by yet an email telling me to release my instance. This has happened to quite a few people. Meanwhile, some who requested a new instance last year are on the new DC.
Is there a date from which all new requested PDIs will be in the new DC?

Jim V
Tera Explorer

Having supposedly lost my old PDI through retirement following the migration notification email.. when I tried to access the new PDI from my SN developer account I was automatically re-directed to the old PDI. The new credentials provided didn't work on the new PDI when accessed by hand. Was able to log on to the old PDI with my previous credentials. This occurred several days ago i.e. well before this blog post. Right now - because it was impossible to actually log in to the newly-provided instance, that new instance has now expired from inactivity. I can still log into the original PDI even though there is no link to it from my SN developer account. But - having made the data centre check as in this blog - it seems probable/certain that this old PDI will be truly retired in February. So - I'll request a second new instance and hopefully everything will finally be OK. Hope ServiceNow really does learn from this shambles. BTW - the Report link from the developer account didn't work either....[Update: new instance requested yesterday matches one of the cluster nodes indicating a successfully migrated instance so now expect everything to be OK]

Lily Li
ServiceNow Employee

@paulmorris @Jim V Thank you for bringing this to our attention. We've shared this concern with our engineering team. In the meantime, please ensure you regularly back up your PDIs while we assess whether this issue will persist during the migration period. Remember to subscribe to this blog, as I'll post updates with the latest developments. Again, thank you for your patience and working with us on this migration. 

Mark Roethof
Tera Patron

How can I get a new instance in the correct data centre AND keeping my old instance number? I did try today to reset and wipe, though that doesn't seem to help.

arnabbhaumik
Tera Contributor

Problem is that we also dont remember every single customisation we did maybe 6 years back and now we need to backup all. Is there any possibility to backup the whole instance in one go like it happens during upgrade or somehow without going to  GitHub or elsewhere ?

 

Jim Coyne
Kilo Patron

I just want to make sure that any instance in the new data centers (ord191 and aus191) are in fact safe and we shouldn't have to worry about them disappearing because of some new reset of the new DCs or something.

 

I do backup regularly to GitHub because there is no guarantee the instances will always be in operational condition and that will continue, but this whole move has been confusing. The original email I received said "The instance has technical issues and must be retired."  Although that might be technically correct, SN should have been more transparent and explained about the move.  I released it, got a new one in the ord191 DC, but received another email about releasing the instance.  So I was concerned but just waited to see what would happen because I had everything backed up anyways.  And then received an email today about the move.  That email should have had a link to this post or somewhere else explaining how to backup an instance.

 

All that being said, I do appreciate the PRIVILEGE of having a FREE fully-functioning instance that I can use to improve my skills.  So thanks to SN for that.

Vladimir Chere1
Tera Contributor

I have wiped and released my old instance and requested a new one two weeks ago. Тhe new one is apparently hosted in the new datacenter based on the description above (aus191).

Today I have got a message from ServiceNow that my instance is going to be revoked (again)??? Is that a "planned" message based on old account/PDI data set that is send without a real time check about where the current account's PDI is ?

 

It would be quite unfortunate if the actual pipeline revoking the instances is also utilising such historical data. I really hope I don't need to restore it again.

Not applicable

I received the notice on Thursday 1/25  that I had until 2/1 to back up my PDI.  I went to backup on Friday 1/26 and it was already revoked!  I fully understand why revocation had to occur and the move of the data center, but the fact that the notice came out and gave ample notice that wasn't afforded is what my frustration is.....

Not applicable

@Lily Li 

Today my PDi was lost, i requested another one, now the problem is it won't let me login!!

I have done with Resetting the password, but it's of no help.

What a worst Experience one can ever face!! This is too bad!!

i keeping getting below:

SandeepDutta_0-1706416244220.png

 

Not applicable

it just doesn't work using "Start Building" button on developer portal.