Workflow path silently gets ignored

Proble

In a workflow run a task does silently not get executed even tough one  task link fulfils its condition.
task_correctly_not_run(1)
                         \(a)
                          task_should_have_run(2)
                         /(b)
          task_had_run(3)
                         \(c)
                          task_that_must_not_run(4)

Solution

For tasks (2) of which one input link is not trodden (a) and for which the input links (a, b) are connected with AND, none of the link conditions (a, b) gets evaluated but silently discarded even tough there are predecessors that have run (3). Possibly it is wrong to use AND but one should use OR instead for the link connection in (2).

Command does not get variable values

Problem

The call of a command in a workflow fails. The call gets logged like cmd /c "powershell -NoProfile -InputFormat none -ExecutionPolicy Bypass -File $$InfaCoreDir\scripts\set_to_rerunnable_only.ps1 - $$ParamDir\wf_B_INIT_OBJECTS_PERSON.par. The variable values get provided by a parameter file but are not passed to the call.

Solution

Wrap the command with a session which in turn calls a mapping that's only purpose is to define mapping variables or parameters being used in the call of the command.

Naming of load groups in single mapping

One can have several load paths (groups) independent from each other in a single mapping. There are conditions where the load order gets set back to some obscure default, e. g. when a source gets exchanged. Therefore it is quite sensible to mark the load order in the name of the source instance or the targets (or both). For instance one could append a LG<number> to the name.