Reproducible context
Distinguish expected behavior from observed results and include timing, steps and recent changes. Read detection, execution, skips and failures as a sequence rather than isolating the final error line.
Troubleshooting & recovery
Logs & full diagnostics
Build a reviewable issue description from operation timing, errors and environment context. Diagnostics reduce reproduction and investigation effort; more data is not automatically better, and upload success is not a fix.
Mechanisms and technical considerations
Data and failure evidence
Diagnostics help review execution paths and failure conditions, but an absent log entry does not prove an event never occurred. Assembly, upload and investigation are separate stages; assembly failure means the report was not uploaded.
Privacy and minimal disclosure
Review the data list and explicitly consent before sending. Share retrieval codes, full logs and account details only through verified private channels. If upload fails, begin with a summary or redacted excerpt rather than exposing raw data.
Validation method
- Record expected and observed behavior, timing and reproducible steps.
- Review the proposed data and upload only after confirming it is necessary and you consent.
- Retain the retrieval code only after confirmed success, share privately and verify any fix through retesting.