Troubleshoot DevOps Center Errors

Provide General Feedback

If you want to provide general feedback, use the DevOps Center Trailblazer group. You can also use the group to request product enhancements, start discussions with other DevOps Center users or the product team, and share best practices.

Issue: User interface doesn’t respond

You notice the DevOps Center user interface doesn’t change after you perform an action. For example, the Create Review button remains disabled after you perform a commit.

Cause: If you have Lightning Web Security (LWS) disabled, it can interfere with the user interface’s ability to respond to a user action.

Action: Refresh the DevOps Center browser page. Alternately, you can enable LWS to avoid this issue.

Error: Pushing Failed

When promoting changes, the promotion fails and you see the “Pushing Failed” error.

Cause: It’s likely that an access token timed out during the promotion process. In this case, the changes were deployed to the target org but weren’t merged to the pipeline stage’s branch.

Action: See if the changes were deployed to the target org. If you see that changes weren’t deployed on the Deployment Status Setup page, the promotion is stalled. See Stalled Promotions to continue.

• Launch the target org. From Setup, find and select Deployment Status.
• If the changes were deployed, go to the source control repository and merge the change (pull) request. The changes are now reflected in the pipeline stage’s branch.
• Back in DevOps Center, go to the Pipelines Stages page and complete the promotion. The changes are redeployed to the target org.

Issue: DevOps Center doesn’t load

When you launch DevOps Center, you see a spinner but the Project page never loads.

Cause: If you installed the Salesforce Page Optimizer Chrome extension, it’s not compatible with DevOps Center. We plan to fix this issue in a future release.

Action: Remove or disable the extension.

Error: Promotion Stopped Due to New Events dialog

The promotion was stopped and you see the Promotion Stopped Due to New Events dialog. Sometimes you see this dialog along with the “Too many SOQL queries” red banner.

Cause: DevOps Center can’t proceed with the promotion because it’s still processing events from the source control system. These events are required for this promotion to succeed.

Action: See Error: Promotion Stopped Due to New Events Dialog for step-by-step instructions.

Error: sf_devops:Too many callouts: 101

Cause: DevOps Center can’t proceed with the promotion because it’s still processing events from the source control system.

Action: See Error: sf_devops:Too many callouts: 101 for step-by-step instructions.

Error: sf_devops:Too many SOQL queries: 101

You see this error when trying to promote individual work items in a non-bundled stage:

sf_devops.AsyncOperationResultCleanup: System.LimitException: sf_devops:Too many SOQL queries: 101

Cause: You have many work items in a non-bundled stage, or you’re trying to promote more than 30 individual work items in a pipeline stage or 20 work items from the Approved Work Items lists.

Action: Promote fewer work items at a time. If you haven’t yet promoted the work items to the first pipeline stage, see Work Item Management. It provides tips on how to reduce the number of work items you’re managing for changes you don’t plan to promote in the near future.

Error: stalled commit

Cause: A stalled commit can occur when updates from external services back to DevOps Center are interrupted during the commit operation.

Action: Determine whether the commit succeeded or failed so you know how to fix it. See Stalled Commits for details. Alternatively, change the Status of the work item to Never, and then start again with a new work item.

Error: Stalled Promotion

Cause: A stalled promotion can occur when updates from external services back to DevOps Center are interrupted during deploy or merge operations.

Action: Determine where the error occurred so you can fix it. See Stalled Promotions for details.

Error: There was an error. Please reload the page...

You see this error when trying to add an environment to the project.

Cause: If Session Security “Level Required at Login” is set to High Assurance, it prevents the use of asynchronous processing.

Action: Ask a Salesforce admin to turn off high assurance for Manage Auth. Providers.

• From Setup, enter Identity Verification in the Quick Find box, then select Identity Verification.
• Under Session Security Level Policies, for Manage Auth. Providers, select None.
• Click Save.

Error: There was an internal data model error. Please reload the page...

You see a work item that indicates that it’s externally merged but you didn’t externally merge it. When you attempt to complete the promotion, you see a red banner with the “internal data model” error message.

Cause: Due to event processing delays, a duplicate Work Item Promote (WIP) record was erroneously created.

Action: Find and delete the duplicate Work Item Promote record. See Error: There was an internal data model error. Please reload the page... for step-by-step instructions.

Error: Ending position out of bounds: -1

You see this error when committing changes or performing some other operation.

Cause: If Session Security “Level Required at Login” is set to High Assurance, it prevents the use of asynchronous processing.

Action: Ask a Salesforce admin to turn off high assurance for Manage Auth. Providers.

• From Setup, enter Identity Verification in the Quick Find box, then select Identity Verification.
• Under Session Security Level Policies, for Manage Auth. Providers, select None.
• Click Save.

Error: Lightning Web Security: Resource loader error loading <...//devopsCenterResources/devopsCenterCSSOverride.css>

Cause: You see this error when launching a project or trying to access your work item list. Enabling Test Run for Secure Static Resources for Lightning Components is incompatible with DevOps Center.

Action: Disable test run:

• From Setup, enter Release Updates in the Quick Find box, then select Release Updates.
• Click Get Started.
• Click Disable Test Run.

Error: Bad_OAuth_Token

Cause: When you try to perform an action from within DevOps Center, such as committing or promoting changes, an error indicates that you have a bad OAuth token. Due to the underlying technologies that support creating sessions that allow DevOps Center to interact with multiple environments in a project’s pipeline, IP addresses aren’t static. Therefore, Lock sessions to the IP address from which they originated must be disabled.

Action: Ask a Salesforce admin to disable the setting in the org in which DevOps Center is installed. See Salesforce Help: Configure Session Settings for details.

Error: Did You Log In to the Correct Environment?

Cause: DevOps Center acts like you didn’t log into the correct sandbox. In Winter ’23, Salesforce launched Enhanced Domains, which changed sandbox My Domain URL formats to conform to new security standards. When you connect a sandbox in DevOps Center, DevOps Center uses a named credential to facilitate authentication. During the release transition, the named credential will likely require updating after the sandbox is upgraded to the Winter ’23 release.

This issue surfaces when you try to perform an action using the sandbox. Actions include opening a connected sandbox, pulling changes from a connected environment, or promoting changes to the environment.

Action: A user with Salesforce admin privileges or the “Customize Application” user permission can update named credentials. After the named credentials are updated, you’re prompted to reauthenticate when you perform an operation against any affected sandbox. See Troubleshoot DevOps Center Configuration for step-by-step instructions.

Error: Can't pull changes from a Developer or Developer Pro sandbox

Cause: Developer sandboxes require that source tracking is enabled.

• In the work item, when you select the non-source-tracked sandbox as your development environment, you see Cannot determine files available to pull - Log in to development environment. Nothing happens if you attempt to log in.
• When you click Pull Changes, you see an error message: There was an error. Please reload the page or contact your system administrator if the problem persists.

Action: See “If You Connect to a Non-Source-Tracked Sandbox” in Pull Changes from the Development Environment for options on how to work around this issue.

Error: Some DevOps Center fields aren’t viewable or editable

Cause: Check to see if you turned on encryption for custom fields in managed packages in the org in which DevOps Center is installed.

Action: Disable this option before installing the DevOps Center package. See Salesforce Help: Encrypt Custom Fields in Installed Managed Packages.

Error: “The request was invalid. Resource protected by organization SAML enforcement.”

Cause: GitHub repos owned by an organization aren’t visible in DevOps Center until an organization account owner provides access.

Action: See Salesforce Help: If an Organization Owns the GitHub Repo for instructions on working around this issue.

Error: “The request was invalid. URL does not reference a valid SFDX project. projectUrl”

Cause: A project repository must contain a Salesforce DX project to work with DevOps Center. The easiest way to create a repository is to use a template we provide in GitHub to create your project repository.

Action: Log in to GitHub and use the provided repository template at github.com/forcedotcom/dx-empty to create your project repository. See your team manager for assistance.

Error: no CustomObject named DevopsEnvironment found or no CustomObject named DevopsRequestInfo found

Cause: Metadata deployment from a sandbox to a production org fails because the DevopsEnvironment and DevopsRequestInfo objects are available only in your sandbox. These objects are used to manage commit, metadata, and data deployment features. You can only deploy them to a production org with the required permissions.

Action: Before you commit or deploy changes, manually remove the DevopsEnvironment and DevopsRequestInfo objects from the metadata XML file.

If you use DX Inspector, you can exclude these objects through the UI. Go to the Change Management page and deselect the DevopsEnvironment and DevopsRequestInfo objects from your change list.