Pull from salesforce failure

in almost 90% of tries, I am not able to pull the last state from the ORG. After creating a new project, I am able to pull it sometimes. This is happening in cases when there is no maintainance. It would be nice If there would be a progress information presentation like for example like 

    Class Pulling Progress 11/94

    Page Pulling Progress 33/62

And after complete:

    Class Pulling Progress 90/94            (4 failed - details button retry button)

    Page Pulling Progress 60/62            (2 failed - details button, retry button) 

I have been doing this in async, and took not that long. If This information could be added very easily if you define everything in the VierwModel

I am aware that resources can be restricted due to editing, but then thos could be skipped. Now if a resource is reserved the whole pull will fail and the not reserved changed files will not be updated

I was trying for an hour to pull from SF. When trying to stop it the Suite just died. 

On the next attempt I received a msgbox saying "Sequence contains no matching element" and the suite died.

Hi ikljaic,

Thanks for providing us the feedback.

If I understand you correctly we can break this as a 2 actions:

• Pull is not working for you
• You'd like to have a visual representation of the pull process

Is this correct?

The team is currently investigating some issues with Pull functionality and we aim to provide fixes for them in the upcoming release in 1-2 days.

Regarding process visualization - it definitely makes sense and I'll add this to our backlog, however I won't promise that this would be implemented before Dreamforce.

Thanks,

Vladimir

Exactly.

I just noticed something, and it might be that this is the reason of pull failures. I have tried not a couple of times and it worked so far.
First I pull from SF and deselect everything, and the files are being deleted that are supposed to be deleted. afterward I pull everything from SF and the pull of classes, triggers, etc works fine.

Maybe the deleting is the issue, why it tends to break.

Hi ikljaic,

Thanks for sharing additional info!

We've already done some fixes for edge cases when Pull process have failed and will release this fixes in coming days.

However we've decided to spend a bit more time on improving/refactoring/fixing Pull process in the upcoming sprint, so most of the fixes would be released on August 10-11.

Anyway I'll kindly ask you to check if your issue would be fixed after the next version update and please don't hesitate to report us any strange behavior, issues or your ideas about pull process.

Thanks,

Vladimir