Loading
Prepare for Email to Become the Default Login ExperienceRead More
Govern, Manage, and Release Changes with DevOps Center
Error: sf_devops:Too many callouts: 101

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.

  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.

      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.
    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.
      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.
    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.
 
Loading
Salesforce Help | Article