Two plugin steps at the same execution order writing one column

Tied plugin steps write the same column in undefined order.

Two steps on the same table, message, and stage share an execution order and write overlapping columns, so the final value is nondeterministic and can flip after a redeploy or import.

Group your steps by table, message and stage, then look for shared execution-order values within a group. Where two tied steps write the same column, the winner is undefined and can change after a re-import. Symptom is a value that differs depending on who saved.

Give the steps distinct execution orders, placing the one that should win last.

This one is environment health, so it carries a plain label and no control mapping. Presenting an operational gap as a security finding would make the real security findings harder to trust, so we keep the two apart.

• A plugin step that re-triggers itself on every save
• A plugin registered twice on the same message
• An update plugin step with no filtering attributes
• A plugin step on Retrieve or RetrieveMultiple