A Power Automate trigger with no column filter

Dataverse flow trigger fires on every column change.

An Update trigger with no selected columns runs on every column change, which autosave multiplies, spending run capacity and feeding re-trigger loops. The flow-plane version of an unfiltered Update step.

Open the trigger in the designer and check Select columns, or export the solution and look for a filtering attributes parameter in the trigger's definition JSON. Its complete absence is the finding, and it is easy to miss because the flow works correctly, just far more often than it needs to.

Set the trigger's Select columns to only the columns the flow reacts to.

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