Flow Designer: wait for condition timeout hours displaying incorrectly days on execution context. - Known Error

Flow Designer: wait for condition timeout hours displaying incorrectly days on execution context. Description When creating Wait for Condition on Flow Designer and enable the timeout option, the setting hours are showing inaccurate days on execution context.

Steps to Reproduce

When creating Wait for Condition on Flow Designer and enable the timeout option, the setting hours are showing inaccurate days on execution context.

Steps to reproduce :

1) set local machine timezone is UTC +1 and above, sample like Australia/Sydney (UTC+10).

1) Hop on instance or impersonate any user which has flow designer permission.. user profile timezone does not affect the result. 2) Open Flow Designer to create new subflow 2) Set input variable as reference.incident , 3) Add wait for condition on record is input , condition to short description is kdsfjjshkfdsjfhs.. 4) Enable timeout checkbox..Input 120 hours , timezone can be selected or blank, it does not affect the result.

Run Test run, choose any incident , then run, check execution, the wait for condition is showing 4 days.. Then change some other timeout hours:

The results are below: 119 hours : showing 4 days 23 hours. (correct) 120 hours: showing 4 days. (incorrect, should be 5 days) 129 hours: showing 4 days 9 hours. (should be 5 days 9 hours) 130 hours: showing 5 days 10 hours.. (correct)

Same behaviour when create this in flow.

Workaround This issue is under review. To receive notifications when more information is available, subscribe to this Known Error article by clicking the Subscribe button at the top right of the article. If you are able to upgrade, review the Fixed In and Intended Fix Version fields to determine whether any versions have or are planned to have a permanent fix.