A bit of context. We have a parent job, which calls a transformation which eventually retrieves and processes an XML file from a service, and then determines if there is a "next link" in the xml and then retrieves this next link, puts it in a parameter and then ends the transformation. This all works fine.
In the parent job itself we call the transformation, then in the next step we evaluate the link variable. if it is empty, we abort the job, else we continue to succes. Then we put the job via start on an infinite repeat until the link is empty and the job is aborted.
Also works fine.
The only issue we have is that the "abort job" will keep triggering a line in the logging of the job, which mentions it as an error (and thus triggering our monitoring software). While in reality it is not really an error. Its just an abortion of the infinite loop since a condition is met (in this case no further links).
I can rename the abort job step, and give it a descriptive message, but it will keep mentioning it as error in the logging. Is there a way to circumvent this? Seems a bit weird this is fixed in the message since not all aborts have to be errors.
So that’s not an error, but a warning or an alert. Just use a Write to log step to log that line you need, and end the job with a success step and not an abort.