v2.1.6+Run logic panel fields

Reference for the HCL Universal Orchestrator Run logic panel that describes available fields, validation constraints, Orchestration CLI keywords, and migration mappings.

The Run logic panel appears in the task properties panel of the Graphical Designer. It replaces the legacy Repeat interval section and absorbs the Repeat for each value field from Scheduling options. For details on configuring foreach iteration, see Configuring a foreach task in the Graphical Designer.

Fields

Field Description Visibility
Repeat for each value Configures iterative data processing across a collection or list. Moved from Scheduling options. For full details, see Configuring a foreach task in the Graphical Designer. Always visible.
Run Strategy Dropdown that defines when the run condition is evaluated and whether the task loops. Options: NONE, RUN_IF, WHILE_TRUE, REPEAT_WHILE, REPEAT_UNTIL. Always visible. Defaults to NONE.
Run condition Multi-line text editor with JSONata syntax highlighting. Accepts a boolean expression evaluated at the point defined by the selected strategy. Must return a strict true or false. Hidden and cleared when Run strategy is NONE. Required for all other strategies.
Repeat every Duration string in HH:MM format specifying the interval between loop evaluations or task repetitions. Required for WHILE_TRUE, REPEAT_WHILE, and REPEAT_UNTIL. Optional for RUN_IF when intervals are needed.
Maximum repeats Integer cap on the number of loops or repeating instances. When reached, the loop stops cleanly and HCL Universal Orchestrator logs an LOOP_STOPPED_BY_MAX_ITERATIONS audit record. Hidden when strategy is NONE. Mandatory for all loop strategies unless a Latest start time boundary is defined. Optional for RUN_IF with intervals.
Skip if late Controls behavior when a scheduled run window is missed. Options: Overlap, Immediate, None. Always visible.

Validation constraints

Strategy and run condition
Selecting any run strategy other than NONE requires a valid expression in Run condition.
Loop interval
The strategies WHILE_TRUE, REPEAT_WHILE, and REPEAT_UNTIL require a non-zero Repeat every duration.
Loop safety cap
All loop strategies must be bounded by at least one exit limit: a Maximum Repeats value or a Latest Start Time. If both are absent, HCL Universal Orchestrator rejects the modification with validation error REPEAT_INTERVAL_REQUIRES_LATEST_START_TIME_OR_MAX_ITERATIONS.
Boolean enforcement
The expression in Run condition must return a strict boolean. A non-boolean result — string, number, null, or object — causes the task to transition to FAIL with error code FAILED_PRECONDITION and the parent workflow to abend.

Orchestration CLI keywords

The following table maps run strategies to their Orchestration CLI rerun type keywords and CLI tags. The RUN_IF strategy maps to the RUN_IF keyword. Maximum repeats maps to the MAX_REPEATS keyword, which corresponds to the maxIterations property (integer greater than 0).

Run strategy Rerun type keyword CLI tag
NONE (legacy EVERY) RERUN_EVERY >>rerun every
WHILE_TRUE WHILE_TRUE >>while true
REPEAT_WHILE REPEAT_WHILE >>repeat while
REPEAT_UNTIL REPEAT_UNTIL >>repeat until

HCL Workload Automation migration mapping

When you migrate workload definitions from to HCL Universal Orchestrator, the following automatic mappings apply.

pollingCondition
Maps directly to runCondition without transformation.
Polling condition without a strategy
If a migrated task contains a polling condition but no run strategy, HCL Universal Orchestrator automatically sets runStrategy to REPEAT_UNTIL to preserve identical polling behavior.
pollingInterval
Maps directly to time restrictions. A one-time warning notification is raised during conversion to prompt layout verification.