A synchronous plugin making an outbound call during save

Synchronous plugin step calls an outbound endpoint in the save transaction.

A synchronous step routes to a webhook inside the user's save, so a slow or unreachable endpoint delays or fails every affected save. The same integration run asynchronously carries none of this risk.

List synchronous steps and check which route to a service endpoint or webhook. The symptom users report is intermittently slow saves that nobody can reproduce, because it depends on the remote endpoint's health.

Re-register the step asynchronously unless the caller truly needs the response before the save commits.

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