How to plan patching and upgrade timing<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Plan your patching and upgrade change requests (CHGs) to help promote a smooth transition. This article provides timing considerations and preparation steps. Test your upgrade timing Complete a full test upgrade on at least one non-production instance for accurate timing of the production instance upgrade. Do not exclude any tables. This provides realistic time frames for the production instance and verifies that a sufficient change window is available. Check WAR file versions Verify that the WAR file version is different between the instance and the upgrade server. If the versions are the same, the CHG does not start even if it is scheduled. Plan for potential delays Scheduled jobs may be delayed, which can affect the start time of an upgrade. If delays exceed four hours, a case is automatically created. These delays are rare, but you should account for this risk when planning. You can contact Support to open a case before the four-hour period if you have concerns about the CHG. Understand instance check-in timing Your instances check for the assigned WAR file change hourly by default, but you can change this interval to a higher or lower value. For example, if the instance is set to default and checks in at 23:33, and a CHG is scheduled for 00:00, the CHG does not start at 00:00. The instance checks in again at 00:33, detects the difference in WAR file versions, and starts at 00:33. Trigger an immediate check To help with this timing, select the Check now button before the CHG is scheduled to start. This makes the instance aware of the WAR file difference so the CHG begins immediately at the scheduled time. The following image illustrates this function. Adjust check intervals automatically Alternatively, if you do not want to perform this manual step, you can adjust the scheduled job interval a few hours before the CHG is scheduled. Set the interval of the scheduled job that checks whether an upgrade needs to run to every few minutes. This allows the CHG to start close to the scheduled time. After the upgrade, set the interval back to its previous value to reduce demand on servers. For more information, see How to trigger your instance upgrade. Monitor upgrade progress The CHG starts with a download of the WAR file and updating the upgrade server. This may take 5 to 10 minutes or longer depending on how the instance is configured and customized. Even though the CHG has started, you may not see visible signs of this in the portal. However, you can see activity in the log files. The following image shows an upgrade log on an instance that has an entry when downloading the upgrade artifact.