I have a sequence of job that after some initialisation, starts a job by command line and then execute a loop - the loop executes a command that polls the job status , extracts a status date and tests for if the job has completed by comparing the status date to a system date stored at the start of the job. However we seem to be getting issues where the job fails to enter the loop and jumps to the tasks at the end of the job. I have attached screen shots to this post that show this better than I can probably describe it. The prof stop loop variable is explicitly set to NO before the loop but the loop is never entered.

I have attached a log file with debug enabled

Thanks

Brett

When looking at the setup only thing I can see that could be wrong is that there is a mismatch in Variable comparison. For example, if there is a space in "NO" when setting (in Task) or when checking (in loop).

We created a more simple example so you could compare and test it at your place. I have attached the Job you can import. All you need is to import and then create a folder "test" in c:/. In that folder create a file called "MYNO.txt". Set the text in that file to NO.

Then run the Job. It will continue to loop until you change the value in the file and save it.

---

Hi Support - turned on the additional debugging level on the condition that triggers the setting of the stop loop variable to YES. There is an exception showing in the log converting the string to numeric ? I think

Attached the exported log file to this post

What I want to do is check a numeric in one variable is greater than another - they are in the format

Variable 'rule_chk_datetime' was updated to: 201206191415

The error is not being detected and the loop just permanently executes until the loop max is reached

I need to make this comparison of the two date time strings to detect when the background process has completed and its updated enddate is now greater than the time just before starting the process. Is is possible to allow string comparisons greater or less than ?

Any update - ?

Thanks
Brett.

Could you break it down to something we can test from here. I am thinking about that you create a Job where you can reproduce this that does not require any external material at all. If you then export the Conditions, Job and Variables to us so we can reproduce this.

If you see a conversation error I am pretty sure that this causes the problem.

So, please create a small example which reproduces the error. This would help a lot.

---

Hi - created this sample job - have also sent this by email.

This job shows the problem of the loop not exiting and the debug log msgs

Thanks.

The problem is that both your Variable names that you use in the Condition are wrong:

{USERVAR(rule_chk_Datetime)} should be {USERVAR(rule_chk_datetime)}
{USERVAR(rule_store_date)} should be {USERVAR(rule_store_datetime)}

---

Ok - sorry support - put the example together fairly late one night - so that's my excuse 😁 - I will go back and check my typing skills for the loop I was having problems with.