You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
More a user-error than a bug, but it seems that the App does not like decimals.
My flow was working fine 90 % of the time, and I discovered that the issue with the remaining 10 % was a mistake in my script which, sometimes, resulted in decimals.
These decimals was passed on to “Start countdown timer”.
Supplying a value with point as decimal separator:
The timer starts and runs for the number of seconds specified.
However, if the value on the right side of the decimal separator contains anything other than zeroes, then “Timer has stopped” is called instead of “Timer reaches zero (0)”.
Supplying a value with comma as decimal separator:
The value is set on the timer, but the timer does not run.
The text was updated successfully, but these errors were encountered:
Thanks for the report. Indeed, the app doesn't like decimals . I've made some adjustments in the code, that should resolve this. I will run some tests the coming days to see if it doesn't break anything, and then it will be released.
More a user-error than a bug, but it seems that the App does not like decimals.
My flow was working fine 90 % of the time, and I discovered that the issue with the remaining 10 % was a mistake in my script which, sometimes, resulted in decimals.
These decimals was passed on to “Start countdown timer”.
Supplying a value with point as decimal separator:
The timer starts and runs for the number of seconds specified.
However, if the value on the right side of the decimal separator contains anything other than zeroes, then “Timer has stopped” is called instead of “Timer reaches zero (0)”.
Supplying a value with comma as decimal separator:
The value is set on the timer, but the timer does not run.
The text was updated successfully, but these errors were encountered: