When I first used it I thought that the time settings were a timeout not the check condition timing. Some method should be provided so that if the condition never becomes true the action can timeout with an error code.
In the meantime you can set a var based timer as an OR condition.
%expiry=%TIMES+60
Wait Until %whatiwantisdone OR %TIMES>%expiry
FYI (as I understand it) lots of dragons around relying on waits because the checks for wait actions are prioritized with other actions so the time is not a schedule but a minimum. Meaning that even if your condition is met you could have scenarios where the action completes late, very late, or very very very very late.
Many threads out there around managing timing in tasker. Lots of variability in precision and intensity of resource usage. Hard to have a timing discussion without tying in task priority.
As a software developer myself, this is an absolute "must have" in my book. I'm a bit shocked Pent didn't include this originally, and never ended up doing so.
