Configure your controller instance

task australia Updated Sep 10, 2026 1 min read config-controller-instance.md
Raw file servicenow.com

You must identify one of the instances in your app development pipeline as the controller instance. All communication between the instances in your pipeline, including the deployment order for applications in the pipeline, takes place in the controller instance.

Before you begin

Role required: admin

About this task

Typically, your production instance should be identified as the controller instance. All request and approval records are stored on your controller instance.

Procedure

  1. Navigate to All > App Engine > Pipelines and Deployments > Environments.

  2. When you are configuring your pipeline environments, decide which instance you want to use as the controller, and select the Is Controller? check box for that instance.

    [Omitted image "controller-instance-purple.png"] Alt text: Is Controller? field

  3. Select Save.

    When the workflow for the pipeline runs, the non-production instances communicate with the controller instance to determine to which instance the app should next be deployed.

Parent Topic:Pipelines and Deployments configuration tasks

Search documentation
Search document titles and file paths on the australia branch