Named timers
Updated
A timer counts down without holding execution in place. While one window waits for an action to become ready, the scenario can check another.
Example: an action every 30 seconds
- Add Start Timer with the name harvest, a 30-second duration and a scope.
- In the working loop, execute Check Timer with the same name and scope. Branch on Finished.
- While it is running, continue other checks. Do not replace it with a 30-second wait when other work must continue.
- After the action, use Control Timer → restart. Repeating Start Timer does not reset an existing timer.
Scope and state
- Scenario shares one timer; Current window gives each selected window-list entry its own timer; Key uses a supplied identity.
- Initialize the window list once before iterating it. Replacing the list creates a new timer namespace.
- Not started, Running, Paused and Finished are different states. Checking creates or restarts nothing.
- Time continues during scenario pause. Stop or a new run clears timers; results stored in variables do not refresh themselves.
- Delay waits within the current flow; the simple Timer produces a repeating yes/no. Use the three named nodes for independent identifiable countdowns.