To avoid toggling, I often work with {TRIGGER.VALUE}

Now I have the problem that

({TRIGGER.VALUE}=0 and last(/Server01/vfs.fs.size[D:,pfree])<10) or ({TRIGGER.VALUE}=1 and last(/Server01/vfs.fs.size[D:,pfree])<11) 

no longer works. The trigger is no longer activated under 10.

 
last(/Server01/vfs.fs.size[D:,pfree])<10)
works if the result is under 10.

This senseless trigger goes to PROBLEM, but should not:
({TRIGGER.VALUE}<>0 and {TRIGGER.VALUE}<>1 and last(/Server01/vfs.fs.size[D:,pfree])<10)
So apparently TRIGGER.VALUE is neither 1 nor 0.

Fresh installed appliance and cloned and modiefied trigger has the same issue:

I guess this has been the case since version 7.2.4