John_Yates
ServiceNow Employee
Options
- Post History
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
on
09-05-2025
03:14 PM
- edited
Friday
by
Claire_Conant
A scheduled upgrade or patch doesn't always align with business priorities, testing schedules, or technical readiness. When that happens, you may assume that you need to contact support to request a change. In most cases, you can reschedule eligible upgrades and patches directly through Maintenance Center in Now Support, without opening a support case. Find the situation that matches yours and go to the knowledge article that covers it.
Does this apply to you?
- Your scheduled upgrade to the next major family release (for example, Zurich to Australia) needs a different date or time.
- Your scheduled patch within the same release family (for example, Zurich patch 8 to Zurich patch 9) needs a different date or time.
Keep in mind: Some updates, including certain security-related changes and updates affected by release lifecycle requirements, have additional restrictions.
Find your path
|
|
Your situation
|
What the article covers
|
Article
|
|
1
|
You want to move a scheduled upgrade or patch to a different date or time.
|
The complete steps and screenshots for changing the schedule in Now Support. If timing is your only issue, start here.
|
|
|
2
|
You want to change the target version of a scheduled upgrade.
|
How to change the version you’re upgrading to, with or without a date change.
|
|
|
3
|
Your update is tied to an end-of-life (EOL) program record.
|
The rules for EOL-driven change requests, which differ from a standard reschedule.
|
|
|
4
|
You’re not sure whether your update type can be rescheduled at all.
|
Eligibility and program-level rules, at a higher level than the task-specific articles above.
|
|
|
5
|
You tried to select a version and couldn’t.
|
Common reasons the version picker doesn’t show what you expect.
|
Important: If you’re upgrading to Australia and your MID Servers run an earlier release, automatic MID Server upgrades can fail after the instance moves. This is a documented known error that was fixed in Australia patch 3. If MID Server readiness is why you’re thinking about rescheduling, read the known error article first.
When you need support
A few situations may still require some support, like EOL extension requests, but you can still use Maintenance Center to get help from Support without creating a case.
Once you know which scenario you’re in, the path through Maintenance Center is usually faster than waiting for a customer support response. If none of these scenarios match your circumstances, the Upgrades and Patching forum in the ServiceNow Community is a good place to see how others have handled similar schedule changes.
More info on this topic
- 3,750 Views
