Quote:
Originally Posted by jdobbs
@Mark_Venture
Just so you know, I ran the job using your INI and, sure enough, I got the same error. I've already identified what is happening, now I just have to put my finger on why. I also found out why it is incorrectly reporting the error as 0. I should have it fixed for the next release.
Good bug report. Thanks.
|
Thank you! Glad to know it wasn't just something on my end this time
