Taskavel allows one running timer per user. Starting a timer on another task stops the timer already running for that user. Check the task and My Time Logs to understand what was recorded.
If time was worked but not timed, add a manual entry from My Time Logs. You can then review, edit, delete, or export your entries. Team Time Logs is the aggregate team view, not a replacement for your personal correction workflow.
For MCP users, GetRunningTimer reads current state and StartStopTimetrack supports explicit start and stop actions. Explicit stop does not start a timer when none is running on that task.
Diagnostic sequence
Open the relevant task and check whether its timer is running, then inspect My Time Logs for the recorded entries. If you started a second timer, expect the earlier timer to have stopped. Add or correct a manual entry when the logged duration is incomplete; do not start a timer merely to represent past work.
For a team reporting question, move to Team Time Logs after correcting your personal entries. For a CLI or MCP client, read the running timer first when the desired action is uncertain and use explicit stop when you only want to stop.