I keep getting this message on 2 of my computers. Regardless if I set it to get 2 hours for each work or for a day and 12 hours for each work.

10/7/2020 5:51:40 PM | Rosetta@home | Sending scheduler request: To fetch work.
10/7/2020 5:51:40 PM | Rosetta@home | Requesting new tasks for CPU
10/7/2020 5:51:41 PM | Rosetta@home | Scheduler request completed: got 0 new tasks
10/7/2020 5:51:41 PM | Rosetta@home | No tasks sent
10/7/2020 5:51:41 PM | Rosetta@home | Tasks won't finish in time: BOINC runs 98.9% of the time; computation is enabled 99.9% of that
10/7/2020 5:51:41 PM | Rosetta@home | Project requested delay of 31 seconds

One computer is a 2.93 GHz and the other is 4 GHz.
None of them will get any work from Rosetta.
Note: When I added Rosetta to my 2.93 GHz computer it fetch one WU and after that got this message and never got any more WUs.

Whatever target CPU run time you choose, BOINC thinks each work unit needs 8 hours of CPU time.

You need to increase the resource share for Rosetta@home (relative to all your other projects) to give it a chance to run.

You need to increase the resource share for Rosetta@home

Let's say the resource share is at the lowest % of Rosetta is lower than all the others. That still doesn't explain why it says Won't finish on time.
Resource share is irrelevant for this case.

One of my computers is running only 2 Projects. WCG and Rosetta. Both at 50/50.

This is difficult to debug client-side, as it’s the scheduler on the server that assesses whether a host will be able to complete the work when it decides what tasks to send.

In your BOINC data directory (usually %ProgramData%\BOINC), open the file sched_request_boinc.bakerlab.org_rosetta.xml in a text editor and look for the value <estimated_delay>. What does it say?

<estimated_delay>557233.817498</estimated_delay>

Rosetta is refusing to send your computer tasks because BOINC has calculated that it is going to be busy for the next 6 days with the work it already has.

How many other tasks are ready to start? What are their deadlines and estimated durations? If there isn’t really that much work in the pipeline, restarting BOINC might reset the calculation.

Rosetta is refusing to send your computer tasks because BOINC has calculated that it is going to be busy for the next 6 days with the work it already has.

What? Busy for the next 6 days?
As of right now, Rosetta has "Tasks ready to send 28477". Doesn't look busy to me.

How many other tasks are ready to start? 28477 What are their deadlines and estimated durations? If there isn’t really that much work in the pipeline, restarting BOINC might reset the calculation.

Deadlines are based on CPU speed and then how long it will take for that WU for that based on CPU speed to finish. BOINC does the calculation based on what Rosetta's information gives. Deadlines are usually 2 days longer than when the task can finish. Deadlines that I can choose can be for 2 hours to a day and a half. Setting any of these in any deadline order I still can't get it to grab any tasks. Note: Doesn't matter what CPU speed you have. If you set it to a day and a half you will get the work but the deadline along with the CPU speed the deadline will adjust acoraccordingly and add around 2 days more on to it.

I had no problems with this for years. I haven't got any work for months now.

Rosetta is refusing to send your computer tasks because BOINC has calculated that it is going to be busy for the next 6 days with the work it already has.

Right now, there are two Asteroids tasks with deadlines of October 19 and six World Community Grid tasks due between October 11 and October 17.

There have been no Rosetta tasks for several days until Rosetta sent me one task this evening. That task is projected to take 07:57 to complete. Its deadline is Oct 11, but it has not started crunching yet.

The two Asteroids tasks are 01:21 and 02:28 away from completion.

This computer has been much busier previously and does not seem overly taxed now. The cores are running at 130-134 degrees F.

So I don't understand how this slow-down relates to your suggested explanation.

And at the moment, the server status shows there are only 27,480 tasks ready to be sent out.

S.Gaber
Oldsmar, FL

BOINC, running on your computer, has calculated that your computer is going to be busy for 557 000 seconds ≈ 6 days. That calculation might be correct, or it might be a bug. Either way: given that information, the Rosetta@home server will not send any tasks because they have no chance to meet their deadline – which for every task is 3 days from when it’s delivered. No exceptions, no dynamic adjustment based on observed performance, no user-configurable influence.

What other tasks are queued up on your computer? (Advanced view » Tasks tab)

What other tasks are queued up on your computer? (Advanced view » Tasks tab)

On my 2.93Ghz are WCG and Rosetta. The other is WCG, Rosetta, Einstein, and Albert@Home.

I did let both computers to get Rosetta only for 1 day of work. Meaning I set all other tasks to "Won't get new tasks".
Still, BOINC wouldn't get and work from Rosetta with the same error "Won't finish on time".

You didn’t say how many tasks from the other projects you have, but it sounds like there is a vast backlog. Reducing your store settings to closer to zero will prevent that from happening.

Try letting all your other tasks finish (leaving ‘No new tasks’ selected for those projects), then check the <estimated_delay> value again. Once all the other work is done, that should drop to zero and Rosetta should send you some tasks.