A flow action pointing at a table that cannot be resolved

Flow action references a table Pathix could not resolve.

A flow action targets a table Pathix could not match, so its writes and reads are missing from dependency results. Often an excluded entity or a mistyped name.

Read the entityName on each Dataverse action in your exported flow definitions and confirm the table exists. Watch the singular and plural forms here: actions use the entity set name while triggers use the logical name, so a mismatch is easy to introduce.

Confirm the action targets the table you expect; fix the target or bring the table into scope.

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