You have what looks like an extremely dangerous script here.
You have a Go To Related Records step without any check to confirm that related records actually exist. If there are no related records, the script continues execution as though the GTRR step was skipped--leading to a Replace field contents operation that could be proceeding from the wrong context on the wrong set of records.
Can't tell if that was a factor in what you had happen or not, but I'd add either a test for the existence of related records or a check to make sure no error code was returned by GTRR to be on the safe side here.
Bingo!!! Thank you once again Phil. I overlooked this. I ran one of my backups offline and tested a scenario where the GTRR will surely fail and sure enough you were right; the replace field contents ran anyhow and changes ALL my clock-in times
This serves as a reminder for myself to go back into old scripts and implement safety nets like these. The time of script execution played no role either so that is good news