like this. this blows my mind. there is no transition possible, and the also notice that it probably isn't a transition going back and forward, since technically line 3 of the first never exited the approved state...

Is it possible this workflow was added via bundle? Maybe in two different ones?

I see... but nope, it's just one approval flow that enters in open, on line 6, and then you enter the pending approval state, line 4.. then we ran an MR script that triggered transitions, based on a custom list record field for status. I also checked the approval flow and around the occurrence there were no new modifications for transitions, Idk, I dont have a good explaination for this

Oh - well when you start playing around with triggering transitions via script - this is the risk you take

@KevinJ of Kansas the scary thing is, there is only one active workflow

I'd probably still cancel it and get it back into it.

I see.. I'm just mind blown I think this is absolutely a broken defect

It's probably a defect - but I'm guessing it's only going to impact your account because of a very precise combination of factors - especially if it didn't happen for all of the impacted records.

it actually for that batch, ran close to 15% of records (invoices) ,(within that hour) i'm just gonna create a support case with NS I guess