I have a job that loops through a text file. The file has 54 rows of data.
The job keeps stopping at 35 iterations, like it looses the loop value somehow, because the task that stalls uses the value as its parameter.
I put in a timeout on the task that stalled, and told it to have no error, and it does not continue to pull values from the read task output from 35 on..
I checked the file for bad characters and it is clean.
I split the text file in half (27 rows and 27 rows) and created a second job, then pointed them to the split file.
Now both jobs work perfectly.

My conclusion is that the job is losing the loop values from the read output at 35 iterations, but the loop keeps going.
Any help would be appreciated.. Attached job export.
  LoopJob.zip (5kb) downloaded 56 time(s).

Can anyone reproduce this? I have another job doing the same thing.
Completely different system and a file listing instead of a listed file.
Any help would be appreciated.

Thanks

Had a quick go at this, but could not reproduce the problem. It looped fine over 70 rows. I had to replace the command tasks with something else, so that may be why. I would try to replace the PrevTask output with the specific Id, just to see if there is something fishy going on. Also, the loop has it's own setting for waiting between iterations, so no need for a separate wait task.

If you replace the command tasks with some other task that uses the loop variables, does it still fail?

It still fails when using the explicit output.
I tested this over and over. The loop variable gets lost after 35 iterations.
Please try using a parameter that is the loop value in a command that will fail when the loop value is lost.
Let me know if you see the same thing I am.
The parameter on my execute task is "{LOOP(CurrentValueXArray,0)}"

Ok, I took the loop output variable out of the execute task and it still fails after the same number of iterations.
I'm thinking it has something to do with the number of execution within the loop, because I removed the value that I thought was going blank or incorrect.
It is not losing the value, because I added a write file task that writes the loop value in a filename and inside.
The error code for the failing execute task is 7777 with no output.

You control Max iterations in the loop. It is by default 1000 so it should not be a problem with 35. I am guessing the input in the For each loop is dirty in some way. You can try this by creating a file with 100 rows of just a simple string and then loop with Write file Task.

Check the content of loop in notepad++ for dirty content.

---

I found that if I do not have a foreground executing process in the loop, it goes all the way through.
If I have a foreground execution process anywhere in the loop, it stops at 32 iterations on the foreground task.