Good idea, I was using fallocate on the monitored client to achive a full filesystem, which is set as condition in the Notification Rule. Thats why I am running a ‘cleanup’ script via a SSH command 
.
But I just took the time and tested it with fake check result.
And the following happened:
And this are the log messages triggered by the RECOVERY:
As you can see, they come basically at the same time (9:57), which is the automatically reset, you mentioned.
So, as conslusion, fake check result is not helping at all, it just confirms the initial error/bug? reported by me…