Prepare a useful troubleshooting packet

A concise diagnostic packet should make the environment and failure clear without leaking credentials or unrelated file content. Preserve the exact error wording where safe.

Work through these checks

1. Environment

record OS and app version. Record the evidence or the unresolved question before moving on.

2. Engine

name the tool and interaction mode. Record the evidence or the unresolved question before moving on.

3. Workspace

identify local or sandbox mode. Record the evidence or the unresolved question before moving on.

4. Evidence

include relevant events and reproduction steps. Record the evidence or the unresolved question before moving on.

5. Redaction

remove tokens and personal source content. Record the evidence or the unresolved question before moving on.

Put the checklist to work

Include whether the same tiny task works outside the failing workflow, and describe only checks actually performed.

Keep the checklist beside the task brief and the actual output. Mark a check complete only after inspecting the relevant file, setting or event. If a required check cannot run in the current environment, describe that gap and choose an appropriate next review rather than substituting a confident summary.

A boundary to remember

Do not publish an entire log directory without reviewing what its events contain.

For the corresponding controls and troubleshooting steps, read the desktop help guide. These checks are a practical review aid; adapt them to the specific source material and intended use of your deliverable.