Start/Resume Timer

Lukasz

After the update, the default job doesn’t start on its own when the user logs into Windows. It used to work just fine before.

Version: 2.13.3.0

timo

This is probably because the background task crashes (at least for some users), likely related to this bug report. I will investigate this in more detail and see if it can be fixed or if the fix needs to be done by Microsoft

Stefan

I met the same issue. Unfortunately for me also the Start and Stop based on Activity is not working anymore since the update. Is this also related to the mentioned bug?

timo

Stefan Yes this problem is related - it also depends on the background task.

timo

@Stefan @Lukasz does the problem still happen with app version 2.13.11?

Stefan

Unfortunately for me it it's still not working as expected.
The Timer stops when logging of or shuttding down, but that's all.
Neither it starts automatically after login nor it stops during inactivity.

Stefan

I've tested with Version 2.14.0.0.

timo

thanks for testing. Can you please show what error is shown in the "Event viewer" program on Windows under the "Application" section? (ideally in text form, not as screenshot) - thanks. I will then forward this error to Microsoft as it's a problem they need to solve. From what I udnerstand at the moment, the background task works for most users, but not all. I'm trying to understand what causes the problem for those users where it does not work. Can you please also tell me what Windows version you are using?

Ricardo Back

The only event I found was located here, and it doesn't look like an error:

The text log is this:

Nome do Log:   Microsoft-Windows-TWinUI/Operational
Fonte:         Microsoft-Windows-Immersive-Shell
Data:          08/08/2025 11:47:40
Identificação do Evento:1621
Categoria da Tarefa:(1613)
Nível:         Informações
Palavras-chave:
Usuário:       S0396\s396
Computador:    S0396
Descrição:
Tentativa de ativação do aplicativo 49297T.Partl.ClockOut_jr9bq2af9farr!App. Estado de execução: Attempted activation of the app, 0, A operação foi concluída com êxito..
XML de Evento:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Immersive-Shell" Guid="{315a8872-923e-4ea2-9889-33cd4754bf64}" />
    <EventID>1621</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>1613</Task>
    <Opcode>0</Opcode>
    <Keywords>0x4000000000000000</Keywords>
    <TimeCreated SystemTime="2025-08-08T14:47:40.9312254Z" />
    <EventRecordID>70</EventRecordID>
    <Correlation />
    <Execution ProcessID="4336" ThreadID="19388" />
    <Channel>Microsoft-Windows-TWinUI/Operational</Channel>
    <Computer>S0396</Computer>
    <Security UserID="S-1-5-21-537296563-420963964-965093349-1001" />
  </System>
  <EventData>
    <Data Name="ApplicationId">49297T.Partl.ClockOut_jr9bq2af9farr!App</Data>
    <Data Name="ExecutionState">1</Data>
    <Data Name="AppState">0</Data>
    <Data Name="Result">0</Data>
  </EventData>
</Event>

My Windows info:

Edição	Windows 11 Pro
Versão	23H2
Instalado em	‎20/‎03/‎2025
Compilação do SO	22631.5624
Experiência	Pacote de Experiência de Recursos do Windows 1000.22700.1106.0

If you need more information, I am available.

timo

The error should be showing here (I just noticed there was a crash for me also with v2.14.0):

Stefan

In my Eventlog i can't find such an Error.
Seems all fine there.

I'm also using the same Windows Versions like Ricardo. It's only Enterprise instead of Pro.

Edition Windows 11 Enterprise
Version 23H2
Betriebssystembuild 22631.5624

Ricardo Back

Yeah, even when I was absent for a long time, the timer did not stop, and there was no error recorded in the event log.
I restarted my computer, the application started, the timer did not start, and again no error was logged.

timo

If there's no crash being logged there in the Event viewer, then it sounds like the app is not crashing (like it is for me), but Windows isn't calling the background task. Can you check in the Windows settings that there are no limitations on the background task of WorkingHours? Can you test changing this setting to "Always" and see if it persists?

Can you please also test enabling the notification feature and see if the start/stop button works (the one on the left, not the one with "...and open app"? This button should also launch the background task and start/stop the timer

Ricardo Back

I changed de config for background tasks, terminate the app and started it.
Still not works.
After that, I recorded the video testing the notifications shared with you here (did not work too): https://drive.google.com/file/d/1TSgfC7RByp2a-QYl3_OXMxUKCiXs3ZnH/view?usp=sharing

Stefan

Same here.
Changed background permissions but this did not change the behaviour.
Also the button Start or Stop Work does not work. Only the button "... and open app" is working.

BobFire

Changed background permissions but this did not change the behaviour.
Also the button Start or Stop Work does not work. Only the button "... and open app" is working. Ver: 2.14.0

timo

I have already uploaded a new version 2.14.1 that might improve the situation (but it's still stuck in the Microsoft Store certification process). I am also in contact with Microsoft about how to deal with this background task problem. Reinstalling the app might fix the problem, please make sure to create a database backup before doing so.
Sorry for the troubles!

Edit: 2.14.1 was just approved in the store, please give it a try

Ricardo Back

I just updated to 2.14.1, and it's working normally now. I didn't need to reinstall.
Thank you so much @timo, great job, the app is really great.

timo

Glad it works again for you @Ricardo Back. Can others confirm the same? There was a bug in 2.14.0 that caused this problem to occur in a higher frequency. I'd be interested if the problem is also fixed for those where the problem happened before v2.14.0

Stefan

I can confirm that! All is working fine again since i'm using Version 2.14.1.
Update was sufficient. No reinstalation needed.
Thanks for fixing it! :-)