Skip to main content
Most chat issues come from unclear context, disabled capabilities, missing permissions, or a task that needs a different Sofie surface. Use this page when Sofie answers too generally, does not use the source you expected, creates the wrong artifact, or cannot complete an action.

​
Quick corrections

ProblemSay this
Sofie answered without searchingUse Workspace search for this answer.
Sofie used broad public contextStop using Web search. Use only the selected Workspace and attachments.
Sofie returned a table in chatCreate this as a CoSheet so I can edit and export it.
Sofie rewrote instead of suggestingUse suggestions or comments in the CoDraft instead of direct edits.
Sofie skipped reviewPause before creating, saving, sending, publishing, or concluding.
Sofie lacks contextBefore answering, list the context you are using and what is missing.
The task is too broadUse Plan Mode. Break this into steps and wait for my review.
Check these items:
  • The Workspace is added to the chat.
  • Workspace search is turned on.
  • The files or artifacts you need are included in Workspace search.
  • The prompt names the Workspace and source scope.
  • The question is specific enough for Sofie to search effectively.
Try: 
Use Workspace search in the Fill-finish deviation Workspace. Search for batch record entries, assay deviations, QA triage notes, and related CoMeetings. Return only findings with source names.
Adding a Workspace to chat gives Sofie access to that context. Workspace search tells Sofie to retrieve relevant material from the Workspace knowledge set.

​
Sofie used the wrong sources

This usually means the source boundary was too broad. Correct it directly: 
Do not use the previous web sources. Use only these three attached files and the selected Workspace. Restart the evidence table from those sources.
Ask Sofie to show the source plan before continuing: 
Before answering, list the source set you will use and the source set you will ignore.

​
Sofie did not create the artifact you expected

Name the artifact type and destination. 
Create a CoDraft, not a chat answer. Title it "DI-2026-014 investigation gap memo" and save it to the deviation Workspace after I approve the outline.

Create a CoSheet with columns for source, observation, impact, owner, and next action. Do not leave it as a markdown table.
If the artifact already exists, add it as context or open Sofie Everywhere from that page.

​
Sofie cannot find an item

Check:
  • The title, file name, or Workspace name is correct.
  • You have access to the item.
  • The item is not archived, deleted, or in another Workspace.
  • The item is included in Workspace search if you expect Sofie to retrieve text from it.
  • The item is a type Sofie can use from the current page or chat.
Try a search-first request: 
Search Sofie for items related to "PPQ sampling rationale". Show likely Workspaces, CoDrafts, CoSheets, CoMeetings, and chats before using any of them.

​
Sofie asks for a file that is already in a Workspace

Sofie may ask for a file when it is not in the active context or not included in the searchable Workspace set. Do this:
1

Add the Workspace

Add the Workspace to the current chat or open chat from inside that Workspace.
2

Turn on Workspace search

Use the sliders menu to enable Workspace search.
3

Name the file or folder

Tell Sofie which file, folder, or source type to search.
4

Ask for source confirmation

Ask Sofie to list the files it found before summarizing them.

​
Sofie says it cannot use a connected app

Connected app access depends on the organization, your account connection, and permissions. Check:
  • The integration is enabled for your organization.
  • Your account is connected.
  • The requested source or action is allowed by your permissions.
  • The connected app item is accessible to the connected account.
  • The request is specific enough to identify the external item.
Try: 
Check whether my connected apps can access this source. If not, tell me which connection or permission appears to be missing.

​
Sofie gets stuck in a long task

Long tasks are more reliable when they are broken into steps. Use Plan Mode: 
Use Plan Mode. First gather sources, then create an evidence table, then identify gaps, then propose a CoDraft outline. Wait for my review before creating the CoDraft.
For very large source sets:
  • Use a Workspace instead of pasting long text.
  • Ask Sofie to search focused folders first.
  • Ask for intermediate tables before final narratives.
  • Split broad requests into one source family at a time.

​
Sofie’s answer is too confident

Ask for uncertainty explicitly. 
Revise the answer. Separate confirmed facts, assumptions, unsupported claims, conflicting sources, and questions for SME review.
Use this for:
  • Deviation investigations.
  • CAPA development.
  • Batch record review.
  • Validation protocol drafting.
  • Regulatory or pharmacopoeia research.
  • Quality risk assessment.

​
Sofie created the wrong result

You can redirect the work without starting over. 
Stop. Keep the source findings, but change the output to a CoSheet evidence matrix instead of a CoDraft narrative.

Undo the last direction. Return to the plan and revise step 3 so it uses only Workspace search.

Do not save this version. Show a revised outline in chat first.

​
When to start a new chat

Start a new chat when:
  • The current chat has many unrelated topics.
  • The context indicator is high and the next task needs a clean source set.
  • You need a different Workspace, model, or objective.
  • A past assumption is contaminating the answer.
  • You are moving from exploration to final drafting.
Use Context windows and summarization to decide when to compact, continue, or start fresh.