forcedotcom / forcedotcom/devops-center-feedback
Error, too many callouts on work item promotion
- Dominant language
- No language data
- Stars
- 61
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
**Describe the bug**
I have a project that I'm trying to deploy tickets from my UAT to Staging, however I'm running into the following error:
sf_devops:Too many callouts: 101
My project has 5 stages (dev, integrate, uat, staging, and production) and work items are able to move freely from dev to uat, but are now throwing this error specifically when trying to move to staging. I've tried moving a work item with many components and a work item with one single component so it doesn't appear to be any sort of volume issue.
I've read through what I can see in the generated logs and I can see this callout running 100 times (therefor hitting the error on the next 101st time). I'm unsure why this callout would be run so many times since its returning a 200. It appears to be stuck in some sort of loop, but interestingly only on this stage.
`09:08:03:922 NAMED_CREDENTIAL_REQUEST NamedCallout[Named Credential Id=XXXXXXXXXXXXXXX, Named Credential Name=DevOps_Center_GitHub, Endpoint=https://api.github.com/repos/radianHub/radianHub/compare/d729d98b118314c0a786fbefdde72e1833b0827b...staging, Method=GET, External Credential Type=EXTERNAL, HTTP Header Authorization=Method: Bearer - Credential: xxxxxx, Content-Type=null, Request Size bytes=-1, Retry on 401=True]`
`09:08:04:223 NAMED_CREDENTIAL_RESPONSE NamedCallout[Named Credential Id=XXXXXXXXXXXXXXX, Named Credential Name=DevOps_Center_GitHub, Status Code=200, Content-Type=application/json; charset=utf-8, Response Size bytes=438527, Overall Callout Time ms=1253, Connect Time ms=1`
**To Reproduce**
Steps to reproduce the behavior:
1. Create, build, and deploy a work item from dev environment to uat stage
2. Attempt to promote any work item from uat to staging
**Expected behavior**
Work item to be promoted from the uat stage to the staging stage
**Screenshots**
If applicable, add screenshots to help explain your problem.
**Additional context**
As far as I'm aware this is not happening on any other project with the same pipeline structure.
Contributor guide
Assessment
This issue has not been assessed yet.