When a duration expression is evaluated for the purpose of scheduling, it is evaluated in terms of milliseconds. However, the same evaluation is also displayed when entering the expression. So the simple expression 1 second evaluates to 1000. The problem is far less obvious when math and variables are involved.
This pull request changes all duration units to milliseconds on the frontend when calculating this expression for display. I was not able to find any cases where this problem affects other expressions.
When a duration expression is evaluated for the purpose of scheduling, it is evaluated in terms of milliseconds. However, the same evaluation is also displayed when entering the expression. So the simple expression
1 secondevaluates to1000. The problem is far less obvious when math and variables are involved.This pull request changes all duration units to milliseconds on the frontend when calculating this expression for display. I was not able to find any cases where this problem affects other expressions.
This has been reported numerous times: