Trouble Accessing the Instance for Training

PeachesCB
Mega Contributor
 
8 REPLIES 8

Hi @PeachesCB PDI and a training instance are not the same!

 

If you have a training there is given instance with preinstalled plugins and demo data to use it.

_____
No AI was used in the writing of this post. Pure #GlideFather only

MaxMixali
Mega Sage

 

Trouble Accessing the Instance for Training – ServiceNow Now Learning

 

 

If you’re having issues accessing your ServiceNow training instance (for hands-on labs or course exercises), it’s a common problem that can occur for several reasons — expired credentials, browser settings, or environment provisioning issues.

 


 

 

Common Causes and Fixes

 

 

 

1. Training Instance Not Yet Provisioned

 

 

  • After enrolling in a course with a lab component (e.g., CSA, CIS, or Developer Training), your training instance may take up to 1 hour to be provisioned.

  • You will receive an email from “no-reply@service-now.com” with your instance URL, username, and temporary password.

 

 

👉 Fix:

Check your spam or junk folder for an email titled

 

“Your ServiceNow Training Instance is Ready.”

 

If you haven’t received it after 1 hour, open a Now Learning support ticket (see below).

 


 

 

2. Instance Expired or Inactive

 

 

  • Most training instances are temporary (7–14 days).

  • If you don’t access the instance within the active period, it’s automatically decommissioned.

 

 

👉 Fix:

 

  • Go back to your course on Now Learning → select the module → click “Launch Instance” or “Request New Instance.”

  • If it’s expired, the button will say “Reset Instance” — click it to generate a new one.

 

 


 

 

3. Using the Wrong Credentials

 

 

  • Each training instance uses a unique local login that differs from your Now Learning or SSO credentials.

 

 

👉 Fix:

Use the username and password from your provisioning email (usually admin / temporary password).

If you changed the password and forgot it, reset it using the Forgot Password link on the instance login page.

 


 

 

4. Browser Cache or Security Settings

 

 

  • Some corporate environments block ServiceNow sandbox domains.

 

 

👉 Fix:

 

  • Use a private/incognito window or a different browser.

  • Try using a personal network or hotspot instead of the corporate VPN.

  • Ensure pop-ups are allowed and cookies are enabled.

 

 


 

 

5. Instance URL or Lab ID Not Found

 

 

If your lab URL looks like https://devXXXXX.service-now.com and you receive “Instance not found”:

 

👉 Fix:

 

  • Confirm that the lab session is still active in Now Learning.

  • Click “Launch Instance” again to get the correct link.

  • If it still fails, open a support request.

 

 


 

 

🧭

If Nothing Works — Contact Support

 

 

  1. Go to: ServiceNow Training & Certification Support Portal

  2. Click “Submit a Request.”

  3. Include:

     

    • Course name

    • Lab/Instance URL (if available)

    • Error message or screenshot

    • Your Now Learning email address

     

 

 

Response time: usually within 24–48 hours.

 


 

 

⚙️

Best Practices

 

 

  • Always access the lab directly from Now Learning → Launch Instance (do not bookmark the URL).

  • Log in at least once every 2–3 days during training to keep the instance active.

  • Avoid sharing the lab credentials; it’s a personal sandbox tied to your account.

  • Use Chrome or Edge — Firefox and Safari may cause lab window issues.

 

Hi @MaxMixali,

 

maybe it's time to use less generative AI to post here or to validate it before you do :)))

 

Look, the title is different, the URL is different and the default expiration also...

GlideFather_0-1761301695602.png

 

URL starting DEV... is for a PDI, the training ones looks like this: nowlearning-nlinst0000000-0aaaa-0001.lab.service-now.com/

 

Also, notification with Instance not found seems to be made up and not real.

 

I appreciate your efforts to help, but I noticed how frequently you post here.

Posting 30+ answers in less than 60 min is obvious that it doesn't originate from you and it cannot result differently than being incorrect rubbish. :))

 

Please continue contributing, it's also fine to use gen AI but always validate before posting. And add your own experience and not just generative content.

 

EDIT: and the link doesn't work either:

GlideFather_1-1761302129173.png

 

GlideFather_2-1761302187003.png

https://servicenow.servicenowservices.com/csm?id=training_support 
it doesnt' even remotely seem to be correct 🙂 correct is: 

 

https://learning.servicenow.com/now/lxp/home 

 

 

Please continue contribute but consider the amount, less is actually more in this case...

_____
No AI was used in the writing of this post. Pure #GlideFather only

Hi @MaxMixali - please stop posting inaccurate, unhelpful AI-generated replies. This behaviour doesn't help the community.