forcedotcom / forcedotcom/devops-center-feedback
Every time I try to sync my dev org, DevOps Center gets stuck on "Cloning repository"
- Dominant language
- No language data
- Stars
- 61
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
**Describe the bug**
Every time I try to sync my dev org, DevOps Center gets stuck on "Cloning repository". Eventually this times out (after a few hours) but during this time, it blocks all movement to our integration stage.
What can we do to resolve this issue?
**To Reproduce**
Steps to reproduce the behavior:
1. Click Sync to backfill my dev org
2. Choose only changed items and run local tests.
3. Wait
...
**Expected behavior**
Should backfill and complete with error or success. Even if the backfill completes successfully (by inspecting the deployment status in my dev org), it still shows an error (see below).
**Screenshots**
NA
**Additional context**
A similar issue affects multiple users but not all. It also appears that this sometimes locks up the entire DevOps Center from promoting any changes (greys out the checkboxes) until a timeout occurs.
Here's a partial response I sent to Francisco about about 1 month ago regarding the problem:
> Just now (well, a few hours ago), I received a message that said "Synchronization Failed" when I tried to backfill my org, but when I look at the Deployment Status in my dev org, all metadata was deployed and all tests passed. The "deploy" was successful, yet I received the "Synchronization Failed" after some time. It seems the status is not getting updated correctly for some reason.
>
> I took a look at the Async_Operation_Result__c table and there's a lot of records in there that show "In Progress" with a message that reads "Cloning repository". I believe these records are in error. Look at the dates.
>
> select fields(all) from sf_devops__Async_Operation_Result__c where sf_devops__Status__c = 'In Progress' limit 25
It would be nice if you could publish a schema of the tables, and what they are used for, and perhaps some notes about the records that way end users could go in and troubleshoot the problem themselves.
Contributor guide
Assessment
This issue has not been assessed yet.