wow, didn't notice the snooze/suspend feature....

Just for clarification: snooze stays in effect for 1 hour and then your machine will resume crunching. "Suspend" stays in effect until you hit resume.

There's a boot-up delay feature too set via the cc_config.xml file. Though it was originally designed to help speed up the system start, delaying the BOINC core client service, it can be set to any length of time. There's a hmmm, I've not found how to work around forcing it to start earlier if so desired. Not a simple button, but maybe the activity menu, suspend > run always / based on prefs flip overrides that. Something I'll be testing when thinking of it, it only working when actually booting, not when manually starting the service.

When BOINC runs can be extensively controlled, mouse/keyboard idle, with 6.10.43 even the amount of non-BOINC load i.e. if you need more than e.g. the default 25% of system cycles, BOINC pauses.

As for the snooze, it's indeed fixed 60 minutes... I'd have preferred a variable or maybe options such as 15, 30, 60, 120 minutes, latter to watch a movie for instance, but then BOINC can be set to pause when your media player is loaded. Features galore, nearly a semester course needed to fully understand how it all behaves.

Most importantly though is, that BOINC should operate completely and utterly without contributors noticing, truly set and forget [until the fever hits ;O]. It may not squeeze the last second out of a device, but it's the one pet peeve for volunteers contributing and that in the long run is not gaining anything for distributed computing.

Happy crunching.

Go to the Activity Menu and set the option back to Run Always/Based on Prefs.

Made an FAQ some time ago describing all the various snooze behaviors and operations, if you're interested.