--- title: Auto-upgrade description: The auto-upgrade mechanism automatically upgrades ServiceNow-managed applications and plugins across your instances on a regular schedule without requiring manual intervention. Auto-upgrade applies exclusively to ServiceNow-managed applications and plugins; customer-customized or third-party applications aren't included in automatic upgrades. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/platform-administration/application-manager/um-auto-upgrade.html release: australia product: Application Manager classification: application-manager topic_type: concept last_updated: "2026-09-17" reading_time_minutes: 3 breadcrumb: [Updating apps, Application Manager, Administering applications, Get started, Administer the ServiceNow AI Platform] --- # Auto-upgrade The auto-upgrade mechanism automatically upgrades ServiceNow-managed applications and plugins across your instances on a regular schedule without requiring manual intervention. Auto-upgrade applies exclusively to ServiceNow-managed applications and plugins; customer-customized or third-party applications aren't included in automatic upgrades. Auto-upgrade enables continuous delivery of ServiceNow-managed applications and plugins by automating the upgrade process, eliminating the need for your manual intervention. Instead of waiting for you to manually upgrade each application or plugin, the system automatically schedules and installs upgrades at optimal times, keeping your applications current with minimal effort. **Note:** The auto-upgrade mechanism is disabled by default. You must enable the sn\_app\_auto\_upgr.enabled system property to activate it. ## Key benefits The auto-upgrade feature provides the following benefits: - Enables continuous delivery of ServiceNow-managed applications or plugins by removing the bottleneck of your initiated action. - Distributes installation load across the platform infrastructure by randomizing upgrade schedules within a 24-hour window. - Respects your high-usage periods by enforcing blackout windows during configured times. - Orchestrates multiple application or plugin upgrades in batches, reducing the number of installation operations across instances. ## How it works The auto-upgrade mechanism operates through a combination of polling, scheduling, and batch orchestration to upgrade applications or plugins automatically: - Automated polling: Your instances poll the API every 2 hours to check for pending SN-managed application or plugin upgrades. When new upgrades are available, the system automatically schedules installations within a 24-hour window of publication. - Blackout window enforcement: Control automated polling with blackout windows and system properties. The system honors your configured high-usage periods \(for example, Monday through Friday, 9 AM to 5 PM\) during which no automated installations occur. Instance upgrade schedules are treated as implicit blackout periods to prevent conflicts. You can manage polling frequency and auto-upgrade controls using three system properties in System Properties: - sn\_app\_auto\_upgr.enabled \(master on/off switch\) **Note:** Auto-upgrade is disabled by default. You must enable the sn\_app\_auto\_upgr.enabled property to activate the mechanism. - sn\_appclient.scheduled\_jobs\_config \(polling frequency and operational settings\) - sn\_app\_auto\_upgr.platform\_upgrade\_lookahead\_hours \(platform upgrade detection window\) - Batch install orchestration: New application or plugin upgrade requests are added to existing active batch install plans if the target installation window is still open. If the window has closed, a new batch is created. The system handles multiple applications or plugins in a single batch and includes retry logic for failed installations. - Environment targeting: Application business units specify whether a release targets non-production environments, production environments, or both. Custom target dates can be configured beyond the default 24-hour window. - Read-only enforcement: All ServiceNow-managed application or plugin metadata is enforced as read-only at installation time, overriding any application-level settings to prevent your customizations. ## Auto upgrade failure resolutions If an auto-upgrade installation fails, the system includes retry logic within the batch orchestration process. Depending on the failure, the system may automatically schedule a retry operation. If automatic retry does not resolve the issue, check the following areas: - Verify that the instance is not in a blackout window or explicit instance upgrade schedule during the scheduled installation time. - Check the status of auto-upgrade tasks in the activity log to understand the progress and outcome of installations. For more information about the activity log, see [Application Manager activity log](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-administration/application-manager/app-mgr-activity-log.md). Task status values indicate the stage of the upgrade operation: - Assigned: The batch install plan has been created and the task is queued for execution - In Progress: The batch install plan is currently executing the application or plugin upgrade - Success: The application or plugin upgrade completed successfully - Failed: The application or plugin upgrade failed; review the failure details and configure retry settings if needed - Resolve withdrawn application errors. If an application or plugin version is withdrawn from the store before auto-upgrade installation, the system treats it as a failed installation and displays an error message indicating the application or the plugin is unavailable. Check the error details to determine next steps. **Parent Topic:**[Updating applications](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-administration/application-manager/updating-apps-app-manager.md) **Parent Topic:**[Using Upgrade Console](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-administration/upgrade-management/um-using.md) **Related topics** [Upgrade Console tools]()