Open matthewpomar-at-reddit opened 1 year ago
It's worth noting that many folks on our team are getting error whilst backfill syncing our dev orgs. I'm not referring to deployment errors checking under Deployment Status, rather DevOps Center errors. Today, one of our team members is getting CPU Timeouts shortly after initiating a backfill to her dev org:
Hoping someone can help us sort through all of these backfill sync issues.
Hi @matthewpomar-at-reddit - Thanks for reporting this. Could you tell me the ID of the org where you have Devops Center installed and also the ID of the dev orgs where the backfill failed?
Which options were selected in the Synchronization Options dialog?
Esteban,
I sent you a PM on Trailhead with the IDs you requested. Let me know if you didn't get it for some reason.
Thank you.
@EstebanRomero84 we have other users now getting this CPU timeout issues. Many on the team are unable to backfill sync their dev orgs. Were you able to review the logs to determine the root cause?
In case you didn't see this, @npiccolo
Thanks @ekapner !!
@matthewpomar-at-reddit hope you are doing well !! can you send to me the IDs to check the logs please ?? Thank you very much !
Hi @npiccolo , I sent you a private message on Trailhead with the IDs. Can you confirm you received it?
@matthewpomar-at-reddit I have received it !!! Thank you very much !!! I'll look at it after another investigation I'm finishing =D
@npiccolo more team members are having problems. Our latest issue is an admin initiates a back-fill sync and it shows the sync is queued:
Then after some time, you get:
When you try to view the details of the error, the log never loads and then you get this error:
Strange thing is, checking deployment status in the dev org, there is no history at all. DevOps Center never tried to backfill his dev org.
I will send you the org id via private message related to this issue. Please confirm once you receive it.
Will these backfill bugs be fixed in GA?
@npiccolo are you still looking into this issue, or have you rotated off of support?
Should we hold off on upgrading to the GA version into this issue is resolved?
CC @geomuck
@matthewpomar-at-reddit Hi, Hope you are doing well ! Question, are you trying to back sync to a dev environment with a work item in progress ?? I was only able to catch this error on the logs: ERROR`Attempted Back Sync on DevOpsPePh while it had work items in progress
And then we have an internal error trying to process that message. We will be working on that at least to display the correct message for the user.
Can you confirm if this environment has any work item in progress please.
Thank you
Best regards
Question, are you trying to back sync to a dev environment with a work item in progress ??
@geomuck identified this issue weeks (months?) ago related to DevOpsPePh. If he did try to back sync with work item(s) in progress, it was not intentional (nor should it be possible, right?).
Can you confirm if this environment has any work item in progress please.
My environment, which is the one I refer to my my original post, did not have any in progress work items. Again, I don't believe the UI will let you back sync with WI in progress, right?
Are you seeing other issues?
Should we go ahead and try to upgrade to the GA version, or will this cause additional issues related to this?
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:
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:
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.