Find your people. Pick a challenge. Ship something real. The CreatorCon Hackathon is coming to the Community Pavilion for one epic night. Every skill level, every role welcome. Join us on May 5th and learn more here.

Now Support and stats.do Out of Sync

Derek Jones
Tera Expert

Hello all!

 

This is likely minor, but I just noticed something odd in our test instance.  I was submitting an automated request on the Now Support site and noticed that our test instance showed it was on Australia EA1.  We have Australia on our dev instance but not on our test instance, since our prod is in Zurich.  We had a clone down late last week, so test should be on Zurich, just as I knew that prod was, so I checked in, sure enough, test and prod are both on the same patch level, both on Zurich 4, hot fix 3B.  

I am going to open a support ticket, more as an alert to ServiceNow Support and just in case there's something more to it, but I'd like to post this out here too, in case anyone else has seen it.  Here are some screenshots:

 

Support_view.png

test_patch_view.png

 

1 ACCEPTED SOLUTION

GlideFather
Tera Patron

Hi @Derek Jones,

 

I just checked for all my available client instances and they all have it 1:1 in the support portal and stats.do

So it might be some occasional glitch rather than some global issue, but good that you created a case to inform SN. Please inform us here once you know more

_____
Answers generated by GlideFather. Check for accuracy.

View solution in original post

4 REPLIES 4

GlideFather
Tera Patron

Hi @Derek Jones,

 

I just checked for all my available client instances and they all have it 1:1 in the support portal and stats.do

So it might be some occasional glitch rather than some global issue, but good that you created a case to inform SN. Please inform us here once you know more

_____
Answers generated by GlideFather. Check for accuracy.

Yeah, that's basically what I got from ServiceNow Support.  I opened a ticket—more as a heads-up to ServiceNow than any real concerns that we had—and was told this:  The mismatch you're seeing in Now Support is due to a known behavior following a clone.

@Derek Jones., thank you for sharing the output from ServiceNow

_____
Answers generated by GlideFather. Check for accuracy.

Andrew Colson
Tera Contributor

Could run a cache.do to see if that clears up the old info.