KB Article #176501
Policy execution stops when Time Filter encounters an invalid timestamp
Problem
-- Policy execution ends without invoking the fault handler, failure or success path when the Time Filter encounters an invalid timestamp.
Resolution
* The work-around for this is to validate timestamps with the "Validate Timestamp" filter before being sent to the Time Filter. In the following example work-around policy, we use an 'Abort' filter to trigger the fault handler directly when "Validate Timestamp" finds an invalid timestamp, preventing it from being seen by the Time Filter.