Failed lock releases now log a warning, including when a lock vanished before release.
What's wrong with this entry?
Releasing a task or mailbox lock goes through a shared helper that catches the error and logs a labelled warning. It distinguishes a lock that was already gone at release time, noting that the protected section may have run without exclusivity, from a stale lock directory left behind.
- Labels identify the call site, such as claiming a task, claiming a task with a busy check, or writing to a named recipient's mailbox.
lock was no longer held at release
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
Background task notifications arrive inside a system-reminder
Both mention background task
-
v2.1.235
Several finished background tasks now report as one line
Both mention background task
-
v2.1.236
Background-task notices no longer look like user approval
Both mention background task