This doesn't happen often, but it adds a some uncertainty in running policies. I noticed that if a computer sleeps, or is disconnected from the network while a policy is running the policy will fail.
For example:
Our distribution point is setup through http and we have some policies that update software on faculty laptops. Sometimes a faculty member will open the laptop long enough to just check email, during which jamf does a recurring check in. If a policy is set to run that updates/installs a large package (like AdobeCS6), then the jamf binary begins to download the package. If the computer is then put to sleep while the package is downloaded, the policy fails.
Is there any way to have jamf automatically handle errors like this? Or is it up to us to manually go through all policies and look for error logs to flush?