A Power Pages permission whose parent chain does not terminate

Portal table permission has a parent chain that cannot be resolved.

A permission uses Parent scope but the chain cannot be followed to a root, so its real reach is undetermined: anywhere between nothing and every row.

Either the chain loops, or it names a parent that does not exist, or it declares Parent scope with no parent set. Pathix will not guess in either direction, because guessing narrow would understate exposure and guessing wide would manufacture it. It makes no claim about what the portal runtime does with a broken chain at request time, only that the configuration does not describe a reachable set.

In the Portal Management app, open any Parent-scoped table permission and follow its parent link until the chain terminates. A chain that returns to a permission you have already visited, or points at one that no longer exists, is the finding. Pathix makes no claim about what the runtime does with a broken chain at request time, only that the configuration does not describe a reachable set.

Set a parent permission that resolves to a real scope, or move the permission off Parent scope if the relationship it depended on is gone.

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