---
schema_version: "1"
id: 692e4a2a73a11bf1b1fcee1b5529ef86dc1a1eb0b5a072ad9124dfee4af15553
title: "Error: sf_devops:Too many callouts: 101"
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/devops_center_troubleshooting_too_many_callouts.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.devops_center_troubleshooting_too_many_callouts.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 3b192f856df5bf5c05ce63e229bd9ef4b4c00dfa40fd802369ae999621fcedfc
description: When attempting a promotion, a red banner displays the “too many callouts” error message.
products:
  - Salesforce Platform
release: "264"
---
# Error: sf\_devops:Too many callouts: 101

When attempting a promotion, a red banner displays the “too many callouts” error message.

If you also see the Promotion Stopped Due to New Events dialog, see [Error: Promotion Stopped Due to New Events Dialog](https://help.salesforce.com/s/articleView?id=platform.devops_center_troubleshooting_new_events_detected.htm&release=264.0.0&type=5 "This error can occur if you attempt to promote work items but DevOps Center is processing pending events from the source control system. You sometimes see this dialog in combination with the “Too Many Callouts” error message. To fix this error, you perform a SOQL query to determine if event processing is continuing as expected or has stalled.") instead for troubleshooting instructions.

1. In Pipeline Stages, click the dropdown menu in the target stage, then select **View Branch in Source Control**.
    
    In this example, the target stage is UAT.
2. In GitHub, find the unique ID (SHA) for the latest commit.
    1. Click the Commits history icon, which is a clock next to the total number of commits for this branch.
        
        ![The GitHub UI, where you can click the Commits icon to view a list of commits.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-devops_center-264-0-0-production-enus/166010c3-4c34-4087-92ad-aea917baf524/devops_center/images/ts-github-commits-icon.jpg)
        
        The most recent SHA is listed first.
    2. Click the Copy Full SHA icon.
        
        ![The Commits list in GitHub for the UAT branch. You can click the Copy icon to copy the SHA for later use.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-devops_center-264-0-0-production-enus/166010c3-4c34-4087-92ad-aea917baf524/devops_center/images/ts-github-commits-list.jpg)
    3. Keep the SHA in your clipboard, or paste it in a text file to save it for use in the next step.
3. View the list of branches.
    1. In DevOps Center, in the org URL, delete `sf_devops/DevOpsCenter.app` and replace it with `lightning/o/sf_devops__Branch__c/list`.
        
        ```html
        https://<my-domain>.lightning.force.com/lightning/o/sf_devops__Branch__c/list
        ```
    2. Find the branch record that corresponds to the target branch, for example, recruiting\_app\_uat.
        
        If you don’t see any branches or the repo contains many branches, create a list view to display your branches. To find the exact branch, include the branch name.
        
        ![Branches list view with branch name field added.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-devops_center-264-0-0-production-enus/166010c3-4c34-4087-92ad-aea917baf524/devops_center/images/ts-branches-list-view.jpg)
    3. Delete the existing value for Remote Reference and paste the SHA that you copied.
    4. Update the Remote Reference Date field to the current date and time.
    5. Click **Save**.
4. Promote the work items.