An update plugin step with no filtering attributes
What it is
Update plugin step fires on every column change.
Why it matters
No filtering attributes means the step runs on every update of every column, which autosave multiplies, spending compute and feeding re-trigger loops. Microsoft's guidance calls for filters on every Update step.
Find it yourself
In the Plugin Registration Tool, check the filtering attributes on every step registered on Update. An empty list means it fires on every column change on the row, which autosave then multiplies.
How to fix it
Register filtering attributes for only the columns the step reacts to.
Not a security finding
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.
Pathix checks this across every environment you scan, along with 39 other conditions. Self-hosted in your own Azure, read-only, metadata-only.