In this manual page I read that idle time can be resolved both when one got distracted from the task at hand, and when the session unexpectedly crashed.
The latter is what happened to me (no hamsters involved, though), however I either do not understand the manual, or am doing something incorrect which I cannot spot.
I gather that, after a crash, still there is a line like this one in one's (possibly recovered)
*** <2022-01-10 Mon> :LOGBOOK: CLOCK: [2022-01-10 Mon 14:26]
However, there is no active clock really running, as if one tries
C-c C-x C-o for
org-clock-out, the minibuffer shows the warning about no clock being active.
I understood that
C-c C-x C-z would scan the files in the
org-agenda-files variable to look for hanging clocks, and then propose to ignore, add X minutes and so on, as one can read in the linked manual page.
In my case, the options buffer does show up, however after choosing to ignore (i.e. keep the time) nothing happens to the clocked line, nor any info on the running clock appears in the info line.
Any suggestions as why this is happening?