405a finite scheduling OPs out of sequence

I'm seeing problems today with 405a Global forward finite scheduling job ops out of sequence.

All our OP are defined as Finish-to-start - yet I'm seeing cases of the 2nd OP being scheduled to start (and finish) before the 1st OP is scheduled to even start.

Anyone out there seeing anything like this?

Rob Brown