Nichtraucher (great name for a non-smoker),

Not seeing that with work unit processing, an erratic behavior of what I presume is you looking at the task graphics... I never view them. The other issue is, if you set BOINC to pause when you're active on the computer AND you have not switched on "Leave Application In Memory when suspended" (LAIM), the task will unload each time you use mouse/keyboard. After stopping use, the science app loads again and the task drops back to a previous progress point saved, but from 50 to 10 is too much to understand. If 49.999%, OET would drop back to 37.5% ** since there are 8 progress checkpoints saved.

The extra problem with OET is the very wide variety in runtimes, so it's hard to estimate progress which is computed from what the server projects when assigning the task [Can be 1.5 hours today, can be 30 minutes tomorrow.

What helps getting a smoother and exact progress indication [expressed in time, not percent] is creating a little file with Notepad called app_config.xml and adding these lines

<app_config>
   <app>
      <name>oet1</name>
      <max_concurrent>0</max_concurrent>
      <fraction_done_exact/>
   </app>
   <project_max_concurrent>0</project_max_concurrent>
</app_config>

Place this file in C:\ProgramData\BOINC\projects\www.worldcommunitygrid.org and restart BOINC or the computer. This will use a client function to override the remaining time estimate of the science application.

** On Linux the drop from 50 would be to 30, since progress % is presented in multiples of 10.

Unsure though if this has effect on the percent projection. For sure, unless the issue is caused by the program unloading frequently, I'd not worry about it. If you go to the Result status page and click on the Valid / Pending Validation link of such a result and post a copy of the log, we can read what the task did.