Versions Compared

Old Version 37

changes.mady.by.user Unknown User (ma0)

Saved on

compared with

New Version 38

changes.mady.by.user Unknown User (ma0)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

When ecFlow tries to start a task, it evaluates the trigger expression.
If the condition is correct, the task is started, otherwise the task stays queued.
Triggers can be between tasks, or between families, or a mixture.
Remember the two rules:

...

A node can only have one trigger expression, but very complex expressions can be built (and keep in mind that the triggers of the parent nodes are also implicit triggers).
Sometimes triggers are also used to prevent too many jobs from running at the same time. In this case the use of a limit may be a better solution (we will cover limits later on in the Limits section).
Nodes can be addressed in trigger expressions using full names: /test/f1/t1 refers to the task t1, and /test/f1 refers to the family f1.
In some contexts, ecFlow will accept relative names, such as ../t1.

...