A plugin step registered against a table that no longer exists

Plugin step targets a table outside the scanned metadata.

A step is registered against a table Pathix could not resolve in the scan, so its writes and reads do not appear in dependency results. Often a deleted table with a stale registration.

Take the target table of each registered step and confirm it still exists in your metadata. Registrations survive the deletion of the table they point at, so this accumulates quietly over the years.

Confirm the target exists and is in scope; unregister the step if the table was retired.

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