DSXchange

I have a sequencer that I would like to have loop. Heres the design:
I expect that when the sleep condition is satisfied that the sleep command will run, then the sequencer will run the job1 again - in otherwords loop continuosly until the continue condition is satisfied.

At runtime is that the sequencer does not start the job1 job. Instead, there is an Info event written to the Director log:

DEP_OLCM_BATCH_SEQ..JobControl (@Coordinator): Note: Sequencer 'Seq1' was entered, but never exited

Job1 uses a user variable that is generated when the job starts.

What causes this to occur?

The loop will not work in this way.
If it is required to have in the ETL job, then the start loop and end loop activity can be used.

The loop will not work in this way.
If it is required to have in the ETL job, then the start loop and end loop activity can be used.

Resolved by implementing loop stages - but this required duplicating logic.

I needed to obtain a value from the job before using this in the start loop stage. The the initial logic is duplicated between the loop stages.

Any constructive comments stilll ... around the duplication especially?

StartLoop does not have to be the first activity in a job sequence - there could be any kind of upstream activity (User Variables, Routine, Execute Command) for fetching this value before the loop gets under way.