A Power Pages page whose list or form lookup is never rendered

Page names a list or form that no template ever places.

A web page names a list, basic form or advanced form in its own lookup column, and nothing in the chain of templates that renders the page actually places one. Visitors get a page without it while anyone reading the configuration sees a page that has it.

Setting the lookup does not put the component on the page. It tells the page which one to use, and the template still has to say where it goes. Usually the lookup was set and the template step forgotten, or a template was later rewritten and the placement dropped out of it, which tends to take more than one page with it. Nothing is exposed by this, since a component that never renders gives nobody access to anything, which is why it reports for information rather than as a risk. Pathix reports it only where it can follow the whole render chain: if a template is missing, or builds the name of what it includes while the page is being served, the page is left alone rather than reported on a guess.

Power Pages design studio, compare the page's list or form lookup against what its template actually renders. Verify by opening the page on the site and confirming you see what the configuration says you should.

Decide which half is wrong: place the component in the page's template, or clear the lookup so the configuration stops claiming something the site does not do.

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