Developing in two sandboxes and both of them when I attempt to deploy anything via metadata or tooling API the deployment is stuck in a pending status from 5-60+ minutes.
I have a case open for one sandbox but am now seeing it on cs19.
Curious if anyone else is seeing this. SF says they found an issue in their server logs on one instance but I cannot create a case for the second org.
I do not believe it is due to anything on my end as the deployment is sent and stuck in pending.
Oddly enough, saving a class via the UI works but tooling and metadata deploy seems broke.
UPDATE
Response from R&D is that it is working as expected. Deployments from the Metadata API can no longer be expected to be completed in a timely fashion. It could takes up to several hours. Suggestion was to use tooling which cannot create new classes / vf pages in a documented fashion. Basically the way it has been working for the last 8 years can no longer be expected
Best Answer
So the response from R&D via Support was:
So basically, the delay is working as designed and hour long waits for an IDE to save/deploy a single class is not abnormal despite what we know to be the case.
After pushing the issue on the partner community the answer I received was a little more encouraging yet still vague. At least it has been acknowledged that there IS an issue:
So if you are having issues PLEASE open a case with support even if it gets closed (Or wherever you post your issues) so that if it continues it is known that it is an issue vs just me being crazy :)
As a point of reference - When I posted my case I provided the Deployment ID so at least the logs could be looked into. As other comments suggest there is no pattern. Sometimes it works fin, then so slow for hours, then fine, then 5 minutes later so slow. At least with a deployment ID they can focus the efforts
UPDATE 8-19-2016
Been seeing this on other instances although not to the same degree. Other instances are 5 minutes or so. CS19 seems to be the worst. Update from SF today