Exit Criteria: Time property comparison not working (Number properties work fine)

ryuu

Are there any known issues or things to watch out for when comparing Time-type properties in Exit Criteria?

When I use a Number attribute for the comparison in my Exit Criteria (Exception event with property filters), the Canvas exits correctly as expected.

However, when I switch to comparing a Time field (comparing the event's event_datetime property against a Context variable using "after"), the exit condition never triggers — even when the data appears to meet the condition.

Has anyone run into a similar issue? Any suggestions on what might cause Time comparisons specifically to fail, or best practices for setting them up correctly

Nirnay

Hi @ryuu,
This is usually a data-type or time-zone mismatch, not an Exit Criteria issue.

For a Time comparison to work:

1. Ensure the exception event’s event_datetime property is ingested as Datetime, not a string.
2. Declare the Canvas Context variable explicitly as Time.
3. Pass both values as full, parseable timestamps representing the same instant, ideally normalized to UTC.
4. Use Time → after only for absolute dates. Do not use Day of Year unless the date recurs annually.
5. Confirm the Context variable is populated before the exception event occurs and has not been overwritten by a later Context step.

A string that looks like a timestamp can still fail the comparison. For example, a display-formatted value or a local-time value without a recognized offset may not be treated as Time.

The Number version works because it avoids timestamp parsing and time-zone normalization. I’d validate the actual event-property type first, then inspect the rendered Context value for a format such as 2025-12-25T08:15:30.250-0800.

Hope this helps.