A Power Pages server logic endpoint no one can call

Server logic endpoint has no web role, so nothing can invoke it.

Web roles are the only way to reach a server logic endpoint, and this one has none granted. Nothing can call it: not an anonymous visitor, not a signed-in user, not a Liquid template.

It is worth reporting because the endpoint looks live in the design studio, where nothing marks it as unreachable. The two readings are a half-finished configuration where the role was never attached, and an endpoint whose role was removed with the code left behind. Either way the code is dormant rather than deleted, so it starts running the moment somebody attaches a role, which is the case for reading it as a change to review rather than a file to ignore. Nothing is exposed by an endpoint nobody can invoke, which is why it sits here and carries no control mapping.

Portal Management app, open Server Logic and check the web roles granted on each record. Verify from a session holding every role on the site: if that call is still refused, no role reaches it.

Attach the web role the endpoint was meant for, or delete it. Holding one role-less on purpose is a reasonable way to stage a rollout, and this is the reminder that it is still there.

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
• A cloud flow that re-triggers itself on every run
• Two plugin steps at the same execution order writing one column
• Two flows writing the same column on the same trigger