A different sort of BPA error

Not sure what happened to last Friday’s BPA run in our Test environment. We are identifying the long running projects (we have more than one that takes more than 30 minutes to complete) in Test, and after we inactivated a few of the big ones, were running the full run (normal run time if it completes is about 3 hours) and it ran for 11.5 hours before terminating with a ‘Error’ instead of an ‘ERROR’ like normal. How would it have gotten the status in a different case? (I’m assuming BPA is made of several parts, and one of them reports it slightly differently, it would give me a clue as to the cause of the error if I knew what it was doing at that spot)

Did they happen to pull some code in from E9 :joy:

Makes me wonder sometimes :smiley: