Knowledge Scope, Statuses, and Retries

At a glance

Topic	Details
Best for	Keeping the Knowledge Base trustworthy instead of noisy or half-processed.
Start here	Check scope first, then status, then retry if needed.
Outcome	Knowledge entries that retrieve more reliably later.

Open it now

• Open Brand Studio

Before you start

• Scope is a placement decision. Status is a processing decision. Keep those two ideas separate.
• A source can be valid but still fail processing once. Retry before you give up on it.
• Delete or rewrite weak entries. A noisy knowledge base is worse than a smaller one.

Scope comes before status

Scope	What it affects
Chat + Image	Both answers and visuals.
Chat only	Planning, answers, and text-heavy workflows.
Image only	The visual side of output.

A healthy knowledge base is not just a long list. It is a list you can still trust later.

Statuses you may see

Status	What it means	What to do
Processing	The source was accepted and is still being prepared.	Wait unless it appears stuck for longer than expected.
Ready	The source is available for later retrieval.	Leave it alone unless the content itself is weak.
Failed	The ingestion did not finish correctly.	Retry first. Rebuild only if the retry keeps failing.

When to retry

• A PDF upload failed.
• A long source had a temporary processing problem.
• The source is still correct, but the first ingestion pass did not complete cleanly.

Upload flows are the ones most likely to need patience, status checks, and occasional retries.

A simple review routine

1. Check that the scope matches how the information should be reused.
2. Wait for the source to become Ready.
3. Retry Failed items before you abandon them.
4. Delete or rewrite weak entries that would only add noise later.

Example: A failed product sheet upload

1. The team uploads a PDF product sheet.
2. The source shows Failed.
3. They use Retry instead of rebuilding the whole entry from scratch.
4. Once it becomes Ready, they double-check the scope and keep moving.

Visual walkthrough

Keep the header in view while you confirm which brand and knowledge area you are updating.

The roadmap is a useful checkpoint when you are deciding what still needs attention after an import or interview.

Pasted notes are another common source type, especially when a retry means cleaning up the source text first.

Related articles

• Brand Knowledge Base Overview
• Adding Knowledge from Interviews, Notes, Websites, and PDFs
• Importing a Website into Brand Studio and the Knowledge Base