I've had pretty steady work on this project but work on ms windows seems to have stopped (couple hours ago) while Linux is still getting work. I noticed a message in the event log on a Windows machine "Tasks are committed to other platforms." Just a temporary outage?

Never mind, looks like the work units are flowing again.

The hopper has run out of work again.
This is the second time I have noticed it in the last two weeks.

2018/09/12 07:08:38 PM | World Community Grid | Sending scheduler request: To fetch work.
2018/09/12 07:08:38 PM | World Community Grid | Requesting new tasks for CPU
2018/09/12 07:08:40 PM | World Community Grid | Scheduler request completed: got 0 new tasks
2018/09/12 07:08:40 PM | World Community Grid | No tasks sent
2018/09/12 07:08:40 PM | World Community Grid | No tasks are available for FightAIDS@Home - Phase 2
2018/09/12 07:08:40 PM | World Community Grid | No tasks are available for FightAIDS@Home - Vina
2018/09/12 07:08:40 PM | World Community Grid | No tasks are available for the applications you have selected.
2018/09/12 07:14:46 PM | World Community Grid | Sending scheduler request: To fetch work.
2018/09/12 07:14:46 PM | World Community Grid | Requesting new tasks for CPU
2018/09/12 07:14:49 PM | World Community Grid | Scheduler request completed: got 0 new tasks
2018/09/12 07:14:49 PM | World Community Grid | No tasks sent
2018/09/12 07:14:49 PM | World Community Grid | No tasks are available for FightAIDS@Home - Phase 2
2018/09/12 07:14:49 PM | World Community Grid | No tasks are available for FightAIDS@Home - Vina
2018/09/12 07:14:49 PM | World Community Grid | No tasks are available for the applications you have selected.

I'm seeing that too on multiple machines. A couple of units have trickled in, but not nearly enough to run a full load.

Greetings,

We get alerts on our phones when the supply for a project is low.

For the root cause: We use a scheduling software to run some of the backend processes on our machines. Since FAHB doesn't have a very big queue, if there is a hiccup it runs out within a few hours. What happened today was the scheduler for the backend was giving processing power to other tasks which aren't as CPU intensive, this caused the work unit loader to wait patiently. Since other projects have 48 hours (the current setting) a few hours of waiting isn't going to cause them an issue. For FAHB, this caused an issue. I manually started the createWork and will probably do so again in a few hours as we have a rather large backlog of smaller tasks that need to be completed.

Thanks,
-Uplinger

Due to the outage on Friday (https://www.worldcommunitygrid.org/forums/wcg/viewthread_thread,41140) the geneator for workunits got hung up. However, this was resolved around 19:00UTC on Friday. Let us know if you are experiencing any issues now. Thanks!