Insights, Logs, and I.G.O.R. Diagnostics

Step 1: Stop and Define the Failure
When an edit starts removing content, losing styles, or returning an error, stop repeated changes. Record one affected URL or admin screen, page or template ID, selected element, user role, viewport, exact action, expected result, actual result, and the time of the attempt.

Step 2: Gather Fresh Evidence
Use Insights and fresh browser or PHP logs from the same reproduction. Capture the response status, one relevant console message, active versions, enabled modules, theme, and a screenshot showing the complete control and result. Old errors from another request can send diagnosis in the wrong direction.

Step 3: Protect Private Information
Review what I.G.O.R. will send before submission. Remove passwords, nonces, license keys, payment secrets, application passwords, private messages, database content, raw customer records, and tracking details. Include only the smallest environment and reproduction evidence needed to understand the issue.

Step 4: Submit One Connected Report
Send one complete report, keep follow-up evidence on the same support record, and use History or the known recovery path when appropriate. After a fix, repeat the original action and verify Studio, public output, desktop, mobile, and fresh logs before closing the issue.
