10 concise reference notes for debugging. These are public reference material, not private user records or a transfer of language-model weights.

Reproduce a failure

Record expected behavior, observed behavior, input, environment and version. Reduce the problem to the smallest case that still fails. Retest that same case after the change so the fix addresses the original defect.

Authored reference note; not externally verified product advice · ref-011

Find the first failing boundary

Trace the request through browser, network, proxy, application and storage. Compare outputs at each boundary and find the earliest divergence from the expected behavior. Later failures may be consequences rather than causes.

Authored reference note; not externally verified product advice · ref-012

Browser and command-line differences

A command-line request may omit the browser Origin header, use a new cookie jar or send a different session identifier. If it succeeds while the browser fails, compare request details and client-side initialization before declaring the entire API healthy.

Authored reference note; not externally verified product advice · ref-013

No request sent

If clicking Send creates no network request, inspect disabled controls, initialization state, form handlers and JavaScript errors. Changing the backend cannot fix a request the browser never sent.

Authored reference note; not externally verified product advice · ref-014

Response received but not displayed

When response bytes arrive but the screen stays empty, inspect status handling, event framing, buffering, text decoding and state updates. Verify completion events as well as content events. A rendering defect is different from an empty server response.

Authored reference note; not externally verified product advice · ref-015

Session ownership failures

A stored session identifier may belong to another identity or an older installation. Check the current account cookie and session ownership. Starting a new session can isolate the issue without deleting all authentication state.

Authored reference note; not externally verified product advice · ref-016

Cache and version mismatch

Compare the served index, referenced asset names and actual asset contents with the intended release. An old index paired with new scripts can fail even when the service starts successfully. Test the public path, not only local source files.

Authored reference note; not externally verified product advice · ref-017

Startup race

A health request can arrive before a newly started process begins listening. A bounded retry can distinguish a transient startup race from persistent failure. Only declare success after an actual successful response and behavior check.

Authored reference note; not externally verified product advice · ref-018

Change one variable

When practical, vary one relevant input or configuration setting per experiment. Record each result. Multiple simultaneous changes can restore service without revealing which change mattered, leaving the failure mechanism unresolved.

Authored reference note; not externally verified product advice · ref-019

Symptoms and causes

A workaround changes the visible symptom or routes around a failure. A root-cause fix changes the mechanism producing it. Both can be useful, but label them accurately and retain a follow-up action when only containment is achieved.

Authored reference note; not externally verified product advice · ref-020

In chat, use knowledge: topic. Browse all reference topics.