Does "Run another job" have an execu

I have a job that on the Event "Job Finish" performs the action "Run another job".
This is setup on step 6 of the job properties. The job it is set to run is the
same job as is being run in the first place. My problem is that this mechanism
seems to stop working after 1000-2000 executions. Is there a known issue with
this or is a job calling itself on completion bad practice according to the
documentation?

I have tested the behavior in a simple JAL job I created that has the one line
"Wait(1)". As this causes it to wait only one second before the job ends it
allows the problem to be reproduced in under three hours. I also set it up to
run as asynchronous, detached on scheduler startup. By restarting the scheduler
to get it running I can then simply monitor the icon created in the taskbar to
see when the job disappears.

It surely runs out of stack (stack overflow) which must be causing the job queue to hang (in the best case)

If you want to run a job every second you se a different method such as endless loop
Here is a simple script type job

Dim forever, boolean, true
LoopWhile forever, END_LOOP

Wait 1

// ... here you run the main processing ...
END_LOOP:

: I have a job that on the Event "Job Finish" performs the action
: "Run another job".
: This is setup on step 6 of the job properties. The job it is set to run is
: the
: same job as is being run in the first place. My problem is that this
: mechanism
: seems to stop working after 1000-2000 executions. Is there a known issue with
: this or is a job calling itself on completion bad practice according to the
: documentation?

: I have tested the behavior in a simple JAL job I created that has the one
: line
: "Wait(1)". As this causes it to wait only one second before the job
: ends it
: allows the problem to be reproduced in under three hours. I also set it up to
: run as asynchronous, detached on scheduler startup. By restarting the
: scheduler
: to get it running I can then simply monitor the icon created in the taskbar
: to
: see when the job disappears.

That makes sense. Perhaps a note of this limitation could be added to the
documentation. I will attempt another methodology as you suggest.

: It surely runs out of stack (stack overflow) which must be causing the job
: queue to hang (in the best case)

: If you want to run a job every second you se a different method such as
: endless loop
: Here is a simple script type job

: Dim forever, boolean, true
: LoopWhile forever, END_LOOP

: Wait 1

: // ... here you run the main processing ...
: END_LOOP: