If the progress is calculated as linear, it's going to take 351 hours or 14.93 days. Suspect it's going to time out on pre-programmed flops or on general time out. So, first, check the quorum if the other result has returned and how long it took.

For what I can see the current B type jobs have a factor 20 time out of current average expected flops (bound / est):

<rsc_fpops_est>79878358574728.000000</rsc_fpops_est>
<rsc_fpops_bound>1597567171494560.000000</rsc_fpops_bound>

If it thus came in and the Time To Complete before start was projected e.g. as 20 hours, theory is that it would bounce at 400 hours, but if not a serious loss.

Also check if your CPU is running maximum cycles and not somehow took a easter holiday and running at throttled down power. OR, check if another process is eating time.

let us know.

The follow-up question is: Why did it take you 250 hours or more to start the job, when the deadline is 12 days.

This smells like the next copy is going out sometime today or tomorrow as your result is going to be considered "No Reply". If the extra copy is returned quicker than yours I'm not so sure what credit will be given under current policy.

At any rate, once overdue, your message log is going to warnings and suggestions to abort.