Hello XS_fallwind,
Set local preferences on that computer to use the local time selected by your OS.

For the Work Unit Cache setting in your profile, use the Cache XX extra days of work and let it communicate every 0.1 days. That way it will communicate as soon as the designated time starts and pull down XX days of work (+ 0.1 days).

Lawrence

Hi,

There's an FAQ where I've explained most all how to set the schedule and buffer and added a note v.v. the UTC / Local time query.

Anyone interested or wishing to contribute a special network/crunching scenario is encouraged to post them here. We'll add them to the FAQ if not too 'off the planet' . Having only networking for 1 hour a day is how I used to control my upload/download, flushing work timed so that it fell 1 hour before the UTC 00:00 daily stats time. So for me it is from 01:00 to 02:00 CET, with the cache/additional buffer set to 1.25 days, in case work finished faster there would be some reserve to prevent idle time.

The work fetch quantity per contact was increased some time ago to I think 15. The client scheduler would though try again e.g. 5 minutes later inside that 1 hour network block to fetch more work until the specified buffer is filled. I'd set the connect to a short time in this situation.... per the FAQ example, to also flush any work that is completed within that 1 hour block.

cheers