Issue
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.
Applies to
Issue was introduced in 9.2.8.0, 9.2.6.6, 9.2.4.9, 9.1.5.15
Workaround
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
Resolution
Issue will be fixed in 9.2.9.0, 9.2.8.12, 9.2.6.12, 9.2.4.17, 9.1.5.18
Ticket reference
RCORE-43056
RCORE-43907
Comments
2 comments
Article has been updated
Article has been updated with query to check which chain/step were affected
Please sign in to leave a comment.