Auto-upgrade

  • Release version: Australia
  • Updated July 1, 2026
  • 2 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Auto-upgrade

    The auto-upgrade mechanism in ServiceNow automatically updates ServiceNow-managed applications across your instances on a regular schedule, eliminating the need for manual upgrades. This feature applies only to ServiceNow-managed applications and excludes customer-customized or third-party apps. Auto-upgrade supports continuous delivery by scheduling upgrades at optimal times, ensuring your applications remain current with minimal administrative effort.

    Show full answer Show less

    Key Features

    • Continuous Delivery: Removes manual upgrade bottlenecks by automating application updates.
    • Load Distribution: Randomizes upgrade schedules within a 24-hour window to balance installation load across the platform.
    • Blackout Window Support: Honors configured high-usage periods to prevent upgrades during critical business hours.
    • Batch Upgrade Orchestration: Groups multiple application upgrades into batches, reducing installation operations and including retry logic for failed attempts.
    • Environment Targeting: Allows specification of upgrades for production, non-production, or both environments, with configurable target dates.
    • Read-only Enforcement: Enforces ServiceNow-managed application metadata as read-only during installation to prevent overwriting customizations.
    • Configurable System Properties: Controls polling frequency, enablement, and platform upgrade detection via system properties for flexible management.

    How It Works

    • Polling: Instances poll the ServiceNow API every 2 hours to check for available upgrades.
    • Scheduling: When upgrades are available, installations are scheduled within 24 hours, respecting blackout windows and instance upgrade schedules.
    • Batch Management: Upgrade requests are grouped into batches with retry capabilities to handle failures efficiently.

    Failure Handling and Troubleshooting

    • The system retries failed upgrades automatically within batch orchestration.
    • Check that upgrades are not scheduled during blackout windows or instance upgrade periods.
    • Monitor upgrade task statuses—Assigned, In Progress, Success, or Failed—to track progress and diagnose issues.
    • Address errors related to withdrawn application versions, which are treated as failed installations with error messages indicating unavailability.

    Practical Benefits for ServiceNow Customers

    For ServiceNow customers, auto-upgrade streamlines application maintenance by automating updates while respecting operational constraints such as blackout windows. It reduces manual workload, ensures timely delivery of enhancements and fixes, and provides controlled upgrade orchestration that minimizes disruption. Customers can monitor upgrade progress and handle exceptions through system task statuses and error details, supporting smooth application lifecycle management.

    The auto-upgrade mechanism automatically upgrades ServiceNow-managed applications across your instances on a regular schedule without requiring manual intervention. Auto-upgrade applies exclusively to ServiceNow-managed applications; customer-customized or third-party applications aren't included in automatic upgrades.

    Auto-upgrade enables continuous delivery of ServiceNow-managed applications by automating the upgrade process, eliminating the need for your manual intervention. Instead of waiting for you to manually upgrade each application, the system automatically schedules and installs upgrades at optimal times, keeping your applications current with minimal effort.

    Key benefits

    The auto-upgrade feature provides the following benefits:

    • Enables continuous delivery of ServiceNow-managed applications 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 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 automatically:

    • Automated polling: Your instances poll the API every 2 hours to check for pending SN-managed application 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)
      • 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 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 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 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 to understand the progress and outcome of installations. 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 upgrade
      • Success: The application upgrade completed successfully
      • Failed: The application upgrade failed; review the failure details and configure retry settings if needed
    • Resolve withdrawn application errors. If an application 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 is unavailable. Check the error details to determine next steps.