How to restrict based on previous Backout status

Summary:

Hello All,

I'm currently working on restricting the custom BIP notification based on below scenario.

If an employee benefits is backed out and reprocessed again, the notification should not trigger to benefits team - which means the data should not be availble in the data set. But the issue is once the reprocessed is done the status is changing to STARTED again, so how to restrict based on previous VOIDD or BACKOUT status. In other words, if an employee has VOIDD or BACKOUT status in any of their history transaction, then the employee data should not be fetching even if their status changed to STARTED again.