ERROR REVIEW
Do not diagnose an error code by guesswork.
A code can depend on the product and version. Preserve what was displayed and the conditions around it before deciding whether a retry is safe.
GUIDE
What to capture first
Keep the display verbatimRecord the code, on-screen wording, and time without replacing them with an assumed meaning.
Identify the operation stageNote whether the issue occurred during startup, recognition, method selection, execution, review, or result transfer.
Record the target and environmentCapture the device, OS or build, tool version, and connection method when those details are available.
Preserve evidence before retryingAvoid actions that remove logs or screens, and stop if safe retry conditions are not known.
Pass the facts to the review pathUse signed-in support or the contact guide with the information you preserved.Open contact pathsReview the facts before the cause
Share the preserved information when the current environment needs further review.