the last one for example is created at 813, but starts until 822, even though there are no other processes of the script running

Other scripts/background processes can jump in and process in between the stages of an MR.

ohh I see I thought only if other deployments of the same script were running, they affected the one waiting