Unsure if this is a bug ... but in my Illuminated Cloud plugin (v1.x) I've got it configured to "deploy all modified files" (as per screenshot), so Cmd+S saves any apex files I've changed since I last deployed.
If I change (say) 3 related apex classes and press Cmd+S, it attempts to deploy them onto the sandbox. If this works - all good. If I get back a "FAIL" or "PARTIAL SUCCESS" message, and then fix the one file containing the error and press Cmd+S again, it only tries to save that one apex file rather than all 3 again, and I normally end up with a further error due to dependencies between the files.
If I then go and make a (minor) edit to all 3 files to change the last-modified-timestamp, then it'll try to save them all again the next time I press Cmd+S.
It's like its updating its "last-successful-deployment-timestamp" prematurely when a deployment fails. Is this a bug or is there something I can change to work around this problem?