+x Sercan - 10/20/2025It appears the issue was caused by my use of values.completioncode, which was not set anywhere in <values>; it was supposed to be parameters.completioncode. My use of values.completioncode in that if-statement caused the code to quit working from there and onward, without warning.
+x Dave - 10/20/2025+x Sercan - 10/20/2025It appears the issue was caused by my use of values.completioncode, which was not set anywhere in <values>; it was supposed to be parameters.completioncode. My use of values.completioncode in that if-statement caused the code to quit working from there and onward, without warning.Okay, so is it sorted now? If yes, then I need not spend additional time reformatting and trying to understand that code. It's hard to say in its current state what it's even supposed to do, since it's lacking comments, missing statement separators to ease reading, seems to use if constructs in places where if - else if would seemingly be more appropriate, and gnerally I can't know what the task scripts do or do not do correctly in terms of setting variables.
+x Sercan - 10/20/2025+x Dave - 10/20/2025+x Sercan - 10/20/2025It appears the issue was caused by my use of values.completioncode, which was not set anywhere in <values>; it was supposed to be parameters.completioncode. My use of values.completioncode in that if-statement caused the code to quit working from there and onward, without warning.Okay, so is it sorted now? If yes, then I need not spend additional time reformatting and trying to understand that code. It's hard to say in its current state what it's even supposed to do, since it's lacking comments, missing statement separators to ease reading, seems to use if constructs in places where if - else if would seemingly be more appropriate, and gnerally I can't know what the task scripts do or do not do correctly in terms of setting variables.Yes, it is settled.