You are here:
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 instead for troubleshooting instructions.
- 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.
- In GitHub, find the unique ID (SHA) for the latest commit.
- Click the Commits history icon, which is a clock next to the total number of commits for
this branch.

The most recent SHA is listed first.
- Click the Copy Full SHA icon.

- Keep the SHA in your clipboard, or paste it in a text file to save it for use in the next step.
- Click the Commits history icon, which is a clock next to the total number of commits for
this branch.
- View the list of branches.
- In DevOps Center, in the org URL, delete
sf_devops/DevOpsCenter.appand replace it withlightning/o/sf_devops__Branch__c/list.https://<my-domain>.lightning.force.com/lightning/o/sf_devops__Branch__c/list - 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.

- Delete the existing value for Remote Reference and paste the SHA that you copied.
- Update the Remote Reference Date field to the current date and time.
- Click Save.
- In DevOps Center, in the org URL, delete
- Promote the work items.
