Running into a weird edge case with date comparisons in our DFO routing logic. We need to check if a message arrived on the current business day to trigger a specific skill group.
I’m using DateTimeDiff in an Architect expression to compare the interaction timestamp against the current time. The goal is to see if the difference is less than 1 day. Here is the expression:
DateTimeDiff(CurrentTime(), InteractionStart(), "hours") < 24
The problem is that when the interaction starts and the check runs within the same day, DateTimeDiff seems to evaluate to null or an unexpected value, causing the expression to fail validation or return false. I’ve tried switching to GetDayOfWeek but that doesn’t help with the “same business day” logic since we have split shifts.
Is there a known issue with DateTimeDiff handling zero or near-zero intervals? Or am I missing a specific format string? The documentation is pretty sparse on the return type when the delta is negligible.
Also, GetDayOfWeek returns an integer (1-7), but comparing that against CurrentDayOfWeek() feels brittle if the timezone offset shifts the day boundary unexpectedly. We’re in America/Mexico_City, so the offset is fixed, but the clock logic in Architect seems to default to UTC somewhere in the pipeline.
Any tips on a more reliable way to check “is this interaction from today” without relying on DateTimeDiff?