A plugin registered twice on the same message

Same plugin type registered twice on one message and stage.

The same plugin runs twice on every matching operation, doubling side effects and outbound calls for no benefit. A classic re-import artifact.

List steps grouped by plugin type, message, stage and table, and look for duplicates. Straightforward to spot once listed, and easy to miss in the registration tool's tree view. Usually left behind by a re-import.

Unregister the duplicate, keeping the one with the correct configuration.

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
• Two plugin steps at the same execution order writing one column
• An update plugin step with no filtering attributes
• A plugin step on Retrieve or RetrieveMultiple