Question
Hap
IN
Last activity: 1 Feb 2026 12:41 EST
differenceBetweenDateTimes Function Not Working with custom calendar.
Hi,
We are seeing an issue with the differenceBetweenDateTimes function when calculating business minutes using a non–US Default calendar. (our custom calendar)
Scenario:
-
Business hours configured in the calendar: 8:00 AM – 8:00 PM
-
Function used:
(@differenceBetweenDateTimes(.TaskCompletedDateTime, .TaskCreatedDateTime, true, Param.Calendar)) / 60
Test Data:
-
TaskCreatedDateTime: 11/25/2025 07:57 PM
-
TaskCompletedDateTime: 11/25/2025 08:57 PM
Expected Result:
-
Only the time between 7:57 PM and 8:00 PM falls within business hours
-
Expected business time: 3 minutes (180 seconds)
Actual Result:
-
Function returns 60 minutes (3600 seconds) when a non–US Default calendar is used
-
The same calculation works correctly when using the US Default calendar
HCA Healthcare
US
@saikiranp6808 This happens because your custom calendar is being evaluated in a different time zone than the DateTime values, so 8:57 PM is treated as still inside business hours and the function counts the full 60 minutes. Fix it by setting the Time zone on the custom calendar rule to match the time zone used by .TaskCreatedDateTime / .TaskCompletedDateTime (typically the application/operator time zone, or UTC if you store timestamps in UTC). After the calendar and the timestamps are in the same time zone, @differenceBetweenDateTimes(..., true, Param.Calendar) will stop at the 8:00 PM business end time and return the expected 3 minutes.