Fix for this will be in the next release. You won't need to do anything other than update. This was caused by a change to Time Since Event. Before, it only allowed minutes and seconds, and now it allows hours, minutes and seconds. Rules created before 2.3.1 were blowing up because of that change.
What you posted above had the key clue: in your Settings, state_5 had the value 7:45 -- only minutes and seconds. The rule was wrongly expecting 0:07:45.
