function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion
Jeff LumJeff Lum 

Developer Console sandbox cs15

Is anyone else getting the following errors in the Progress tab in their DC sandboxes?
They show up before anything is opened, prior to that there was an error about Metadata failing to return the correct amount of lines. The prior error corrected itself after 10 days.

Getting all queued deployments for container=undefined
Creating deployment for containerId undefined Save=true runTests=false
Creating or Updating containerMember for containerId=undefined
Best Answer chosen by Shashank (Salesforce Developers) 
Alex KirbyAlex Kirby
Hi Shashank,

I resolved this by createing a new workspace in the org and setting it to default

Through dev console, workspace, new workspace.

Must have been a bug when the org was refreshed / created.

Thanks,

Al

All Answers

ShashankShashank (Salesforce Developers) 
Could you please let me know if you are still faicng this issue?
Jeff LumJeff Lum
Hi Shashak,

Yes the problem is still occuring even after the Sandbox was Refreshed
ShashankShashank (Salesforce Developers) 
Hi Jeff,

Could you please email me at ssrivatsavaya@salesforce.com refering to this post and providing your sandbox and production org IDs?

Thanks,
Shashank
jeff.barnettjeff.barnett
I'm having the same problem.  Did this get resolved? If so, what's the solution?
Alex KirbyAlex Kirby
Created a sandbox yesterday and this problem is occurring, any news?
ShashankShashank (Salesforce Developers) 
Hi Alex,

I will work with Jeff Barnett who posted above regarding reproducing the issue and will let you know the status.

Thanks,
Shashank
Alex KirbyAlex Kirby
Hi Shashank,

I resolved this by createing a new workspace in the org and setting it to default

Through dev console, workspace, new workspace.

Must have been a bug when the org was refreshed / created.

Thanks,

Al
This was selected as the best answer
ShashankShashank (Salesforce Developers) 
Thanks for sharing the solution Alex. Jeff, Please have a look at the solution provided by Alex.
BillHansonBillHanson
This article helped me to get going again! Thank you so much!

In case it helps, this is happenging in all of my orgs (4 sandboxes & 2 production orgs).  Creating a new workspace and deleting the old one fixed the issue in all orgs.