Cannot create a new Project

[srihithacherukuri14]

Describe the bug Unable to create a new project in the DevOps center. We are receiving the error "Too many callouts: 101". We have 100 existing projects and when trying to create the 101st project the error occurs.

To Reproduce Steps to reproduce the behavior:

1. Create the 101st project in DevOps.

Expected behavior Able to create projects beyond 100.

Additional context I deleted the new project, I created in the Salesforce Projects tab and I was able to see the existing projects but still cannot create a new one.

[geomuck]

Ooh good find, thank you! That's almost certainly a bug on our side. I'll get it logged!

Meanwhile: do you need all of the existing 100 projects? If not, I can help walk you through deleting the unneeded Project__c records to prevent this error from happening.

[git2gus[bot]]

Error while creating work item!

[srihithacherukuri14]

That, would be great. We have projects that were created in error and we are unable to delete them.

[geomuck]

W-11968941 is the bug.

[geomuck]

I'll circle back around to this with some guidance as to how to delete Projects as soon as I can!

[geomuck]

OK, you mentioned that "I deleted the new project, I created in the Salesforce Projects tab and I was able to see the existing projects but still cannot create a new one."

Does that mean that you deleted the new Projectc record that was created, putting your back to 100 Projectc records? If so, are there additional unused/unnecessary Project__c records that you can delete as well, to try to get well below the 100-record threshold?

[srihithacherukuri14]

That is correct, I was able to delete the new 101st project as it was not associated with the release environment. I have prepared a list of projects that can be deleted but are associated to the release environment (some have the wrong release environments. If we can delete them we will be under 100 Project records.)

[geomuck]

OK, you should be able to simply delete the Projectc records that you don't need, and the Environmentc records should be cascade-deleted. Do you want to try it out and let us know the results?

[srihithacherukuri14]

I tried it but I am unable to delete the project.

[varunguruvugari]

@geomuck I was also able to reproduce the issue internally. I am unable to delete a project, if i have a pipeline configured even though it is not active.

Here is the error message:

Your Attempt To Delete TEST 2 Could Not Be Completed Because It Is Associated With The Following Pipeline Stages.: Production, UAT, Integration.

[varunguruvugari]

Solution to fix this would be to DELETE "sf_devopsPipelinec" records first and then delete "sf_devopsProjectc" records.

[geomuck]

OK, if there's a Pipeline associated with the Project that you're trying to delete, then you'll need to delete the Pipeline_Stagec records, and then the Pipelinec record, and THEN the Project__c record. Want to give that a try, please?

[srihithacherukuri14]

Thank you, that helped! I was able to delete few projects.

[geomuck]

Excellent! Are you now able to create new Projects?

[SAxcell]

@geomuck We're still running into this issue. We can continue to delete projects, but it's very cumbersome. Is the expectation that an org will have fewer than 100 projects? As you know, we've been using DevOps since the pilot, and we have 7+ users, so 100 projects doens't go very far, even now that we're not making mistakes when we create them. Any thoughts on a way to "complete" a project and somehow have it archive or otherwise not count toward the limit? We're going to start cross training the team from our other Salesforce org (we have separate orgs for Sales/Marketing and Service, with separate admin and dev teams) so that means even more developers and I expect lots of projects created (both intentional and in error) as they learn their way around.