A plugin step on Retrieve or RetrieveMultiple

Plugin step registered on Retrieve or RetrieveMultiple.

These are the hottest messages on the platform, so every list view, lookup, and API read pays the step's cost. Worst when it makes an outbound call on every read.

Filter your step list by message and look for Retrieve and RetrieveMultiple. These are usually deliberate, so the question is not whether the step should exist but whether it is fast enough to sit on every read in the environment.

Move the logic off the read path; if it must stay, keep it fast with no outbound calls or extra queries.

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