NNyquest docs

Conversation and Memory Issues

Use these checks when history is missing, an answer stops early, or remembered context is incomplete or wrong.

A conversation is missing

  • Check the project filter. Open the conversation list and choose All conversations (or the equivalent chassis label).
  • Check the account. Conversations belong to the account that created them.
  • Check whether it was deleted. Confirmed deletion cannot be undone through the app.
  • Allow the list to refresh. The list shows recent conversations; absence from that list alone does not prove deletion. Keep important conversation URLs or exports for your records.

If a conversation still seems missing, contact support with its title, approximate date, and conversation URL if you have it.

An answer stopped halfway through

An Incomplete answer notice means completion was not confirmed or the provider reported a limit or interruption. Received text is kept. Answer unavailable means the request did not produce a completed answer.

  1. Read the notice for the recorded reason.
  2. Use Reload saved answer, if offered. It reads the stored result without another model request.
  3. If the saved result is not available yet, wait briefly and check again. A failed reload keeps the partial output.
  4. If the stored answer is still incomplete, ask the model to continue from the last complete point or request a shorter answer. This sends a new request.

Reloading does not regenerate missing text. Older answers without completion metadata may have an unknown outcome. For code, check that the final block is complete before using it.

“It does not remember what we discussed”

Memory is selective. It is not a full transcript lookup, and saving a conversation does not guarantee that every detail becomes a reusable fact.

  • Name the topic and historical intent. For example: “What did we decide about the database in our previous conversation?”
  • Use a full question. With the default gate, messages under four words skip a new semantic search. Recent context and eligible saved facts can still be supplied.
  • Allow time after a reply. Extraction, summary updates, and indexing run in the background. A failed or rejected extraction can leave a gap without deleting the transcript.
  • Use the right project. Project-specific memories stay within that project; temporary instructions are not automatically global preferences.
  • Check saved facts. Open Settings → What Nyquest remembers. Unpinned facts can be merged or retired by housekeeping. Pinning protects a fact and prioritizes it but does not guarantee selection.
  • Check the original answer. Interrupted or cancelled answers stay in history without being indexed as completed answers for semantic recall.

For an exact quotation or essential constraint, reopen the original conversation or paste the relevant context into your current message.

Memory supplies something stale or wrong

Open the answer's details or Inspect → Memory Context, when available. Check the supplied items, scope, date, author, and source information. A recalled assistant statement is historical context, not independent proof. Memory counts describe supplied context, not factual confidence.

Use Settings → What Nyquest remembers → Forget for a wrong saved fact. Review pinned facts directly: automatic corrections do not replace them. Forgetting an entry does not erase the source conversation or other entries on the same subject.

If source details cannot load, they may have expired: detailed snapshots are available for up to seven days, and older answers may have only partial excerpts. For current facts, check the original evidence or the separate Web Grounding links when available.

An attachment failed or a photo is not understood

  • Wait for every selected attachment to be ready before sending. Use Retry or remove a failed item.
  • For photos, use JPEG, PNG, or WebP; convert HEIC/HEIF first.
  • Stay within 25 MiB per file, 40 megapixels decoded, and five attachments per message.
  • Choose a model that supports image input. This workflow is not available in Splicer or stateless API-key chat.
  • Reopen the same conversation for follow-up questions about a sent photo. If an earlier failed upload says the original is unavailable, attach the original again.

The text of a partial answer and the attachment's upload status are separate. Reloading an answer does not re-upload a missing file. See Using Artifacts in Chat.

Project instructions seem absent

Verify that the intended project is active and its system prompt is configured. Instructions affect future requests; they do not rewrite existing replies. Include a specific instruction in your next message to check the behavior, and see Project-Scoped Chat.

Where to next