Built something you're proud of? Tell the story. A quick G2 review of App Engine or Build Agent helps other developers see what's possible on ServiceNow. Share your experience.

Recovering Expired Rollback Contexts

Go to solution
Jeffrey Beaudry
Kilo Sage

‎01-11-2023 05:53 AM

It was brought to my attention recently that a user made multiple changes to some records on 12/29 that need to be reverted back.

Unfortunately looking at the Rollback Contexts, the item is in a state of 'Expired'.

Is there anyway to recover those contents or are they gone forever?

Thank you.

JeffreyBeaudry_0-1673445173211.png

 

0 Helpfuls
  • 1,828 Views
1 ACCEPTED SOLUTION

Go to solution
Not applicable

‎01-11-2023 07:31 AM

Hi @Jeffrey Beaudry ,

The rollback process on Now Support does the following:

  • Updates the reported WAR to the rolled-back version and the assigned WAR remains set to the version before the rollback.
  • Sets the property glide.war.no_upgrade on the instance is set to the version before the rollback.
  • Displays the message, "Desired war matches reverted war specified by property [glide.war.no_upgrade]. Upgrade script will NOT run".
  • Changes the state to Expired and the rollback purges all stored data.

So, i don't think you would get that working.

 

View solution in original post

1 REPLY 1

Go to solution
Not applicable

‎01-11-2023 07:31 AM

Hi @Jeffrey Beaudry ,

The rollback process on Now Support does the following:

  • Updates the reported WAR to the rolled-back version and the assigned WAR remains set to the version before the rollback.
  • Sets the property glide.war.no_upgrade on the instance is set to the version before the rollback.
  • Displays the message, "Desired war matches reverted war specified by property [glide.war.no_upgrade]. Upgrade script will NOT run".
  • Changes the state to Expired and the rollback purges all stored data.

So, i don't think you would get that working.