Force Save not working as expected if file not saved yet.

[Mike Wannamaker]

I have not tested with anything else, only using apex classes right now. If you edit a class and then hit the shortcut or menu to Force Save, I would expect the action to save the file locally and then deploy to org all in one step. However it only saves the file locally. You then have to hit the shortcut or the menu Force Save again for it to finally deploy to org.

[Scott Wells]

Odd. I'll take a look. I'd also recommend that you consider enabling Override Save All Action if you haven't already which should obviate the need for the Force Save action altogether.

[Mike Wannamaker]

I did not have that checked, I will also try that for a while.

[Mike Wannamaker]

Downgrading severity as the option to override saveall is working for me.

[Scott Wells]

Mike, the only way I've been able to reproduce this is by disabling Deploy on save (as well as Override Save All action):

Otherwise if I do have Deploy on save enabled, what happens is the file is first saved to the filesystem, then the deploy-on-save behavior kicks in and it's deployed to the server.

Can you verify that you're seeing the same behavior when Deploy on save is enabled?

[Scott Wells]

Resolving this based on the last comment. If this can be reproduced when configured in a way other than that, please feel free to reopen with details.