Two live processes must not start on the identical trigger

Control Statement: Two enabled business processes must not start on the same event, for the same record type, under the same condition.

Description: Where two live processes are triggered identically, both run on every qualifying record. Creatio guarantees no order between them, so the outcome depends on which finishes first. This control requires that identical triggers be resolved — by merging the processes, by narrowing one condition, or by disabling the one that is redundant.

Rationale: This is the defect that does not look like one. Each process is correct in isolation and was tested in isolation; the fault appears only when both run, and it appears intermittently, because it depends on timing. Teams lose days to “it only happens sometimes” before anyone thinks to ask whether a second automation is doing the same work. The instance will never report it, because from Creatio’s point of view nothing has gone wrong.

Audit Procedure:

1. Enumerate the enabled business processes and the signal each starts on.
2. Group them by record type, event, watched columns and start condition.
3. Record every group containing more than one process that can currently run.
4. For each group, determine whether both were intended to run on the same records.

Remediation:

1. For each group, decide which process should own the work.
2. Merge the logic, or narrow one condition so the two no longer overlap.
3. Disable the redundant process rather than leaving it enabled and unreachable.
4. Re-check after the change: narrowing one condition can leave a second group behind.

Default Value: Creatio permits any number of processes to start on the same signal and warns about none of them. Execution order between them is not defined.