A Power Pages advanced form step whose target form is missing

Advanced form step points at a form that does not exist.

A step names a form on a table and no form on that table carries that name in this environment. The step has nothing to render, so visitors who reach it get an error instead of the form and every step after it is unreachable.

What a broken binding looks like after a rename, a delete, or a solution layer that was never shipped to this environment. The step stores the form's NAME as plain text rather than a reference to it, so renaming a form silently breaks every step that pointed at it, and a rename usually breaks more than one. Pathix reports only the case where no form matches. Where more than one form on the table shares the name the binding is ambiguous rather than broken, and Pathix deliberately does not report that here or guess which form was meant.

Power Pages design studio, open the advanced form and read each step's target table and form name, then confirm a form of that name exists on that table. Verify by walking the advanced form end to end on the site and confirming every step renders.

Point the step at a form that exists on the target table, or remove the step and reconnect the sequence around it.

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