A connection reference with no connection behind it

Connection reference has flows but no underlying connection.

Flows cannot run through an unbound reference, so enabled ones fail at run time and disabled ones fail to activate. Common after an import skipped the connection wiring.

List connection references and check which have no connection set, then check whether any flow binds to them. Almost always an import artifact, so worth checking straight after any solution deployment.

Bind the reference to a service-account connection and test each flow.

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
• A plugin registered twice on the same message
• An update plugin step with no filtering attributes