To make sure this is understood, with client v7 the 'additional' work buffer is not used until the total buffer level drops below 'minimum'. For example if setting ,5 days minimum plus ,5 days additional, no backfilling will happen until total buffer drops below .5. Generally this stops trickle requesting. Also as soon as the buffer is over minimum, fetching stops. Large additional is pointless anyway at WCG as there's a cap on the workprovision per request and in total of now 35 In Progress per active thread on host.

Anyway, lots of words where you may have meant to say that the higher minimum was fully topped up.

Crowd Crunch On.

To Keith

I read your update in the news:
First is going to be a change to our network infrastructure to update a configuration setting to help correct some of the feeder issues members have noticed. This is scheduled to take the website entirely offline for 8 hours, but I estimate it will be closer to 1 hour.

Do you already know when it will be planned?
The problem prevented one device to report work during almost one day yesterday:
See my post there: https://secure.worldcommunitygrid.org/forums/...ead,37807_offset,0#486147

Hi Erika
I am disappointed then, because the problem occurred again for me on 28/02 and 01/03

During the change on the 28th, we encountered an issue with the rules that were put into place on the 21st outage. To keep the website viewable during the outage on the 28th, we disabled the new rule. It will be going back to being active soon.

Thanks,
-Uplinger

Thanks