Under certain specific timings, it was possible that a Process Chain could run future steps before they should get started. This chance is higher if the chain has preconditions and/or final status handlers.
Issue was introduced in 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52
There is no workaround available.
The following query can be used in a report to see which step may have run too early:
select sj2.JobDefinition as ChainName, sj2.Description as StepName, sj2.JobId, sj2.RunStart
from Job sj, Job sj2
where sj.ParentJob = sj2.ParentJob
and sj.JobChainCall is null
and sj.JobChainStep is not null
and sj2.JobChainCall is null
and sj2.JobChainStep is not null
and sj.ChildOrder = (select max(j.ChildOrder) from Job j where j.ParentJob = sj2.ParentJob and sj2.ChildOrder > j.ChildOrder )
and sj2.RunStart < sj.RunEnd
order by sj2.RunStart desc
Issue will be fixed in 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199