24-04-20 07:50 AM
28-04-20 09:52 AM
28-04-20 02:50 PM
@Mr Right - This has been around since I started using the product back in the version 4 days. We got around it by creating a similar action that performed .25s increment wait stages until it counted up to the desired value. Since it wasn't sleeping the entire time, this allowed other threads to process. It looked something like this:
1) Start
Input: Time (Number)
2) Wait
Condition: None
Time: .25s
3) Calculation: Time++
Value: [countedTime]+.25
Store in: [countedTime]
4) Decision
Condition: [countedTime]>=[Time]
5a) Decision = No, go to step 2
5b) Decision = Yes, go to End
29-04-20 07:21 AM