Conversation Too Long Error

If you see "Your conversation is too long. Please start a new conversation to continue." or "AI service ran into an error. Please try again." when sending a message, you've reached the maximum conversation length that the AI can process.

What Happened?

The combined size of your conversation history, uploaded files, and current message has exceeded the context window for the route serving that request. Exact ceilings vary by plan and provider path (Free enforces its own conversation cap; paid routes differ). Treat the in-app error as authoritative.

Think of it like the AI's "working memory": once the conversation gets too long, the AI can no longer process all the information at once.

Why Did This Happen?

This error typically occurs when you have:

Long Conversation History

Conversations with 100+ messages, especially detailed back-and-forth discussions about complex compliance topics, can accumulate significant context.

Large File Uploads

Files consume a large portion of the context limit, particularly:

• Multi-sheet spreadsheets - Large Excel files with extensive control matrices or detailed requirements can split into 100+ parts when processed
• Lengthy PDF documents - Full policy manuals, standards documentation, or audit reports
• Multiple document uploads - Several files uploaded throughout the conversation

Combination of Both

Extended conversations with many messages combined with large file uploads can exhaust the window even when each individual message seems reasonable.

How to Fix It

1. Start a New Conversation (Recommended)

Your previous conversation is automatically saved and accessible anytime. Simply start a fresh conversation to continue your work.

Steps:

1. Click the ISMS Copilot logo (top left) to return to the welcome screen
2. Start typing your next question in a new conversation
3. Your old conversation remains in your history and workspace

2. Summarize Previous Context

If you need to reference earlier work, copy key findings from your long conversation and include them in your new chat.

Example:

"Based on our previous gap analysis, we identified 12 missing ISO 27001 controls in Annex A.8 (Asset Management). We're implementing a CMDB for A.8.1. Now I need help with A.8.2 (information classification)..."

This gives the AI the context it needs without loading the entire conversation history.

3. Upload Smaller or Fewer Files

For your new conversation, be strategic about file uploads:

• Break large documents into sections - Upload only the relevant pages or tabs you need analyzed
• Limit how many large files share one thread - You can batch up to 10, but for huge packs start a fresh conversation per major analysis
• Convert large spreadsheets - Extract specific worksheets to separate files instead of uploading entire workbooks
• Remove unnecessary content - Delete cover pages, images, or appendices that aren't needed for analysis

4. Use Separate Conversations for Different Topics

Instead of one long conversation covering everything, create focused conversations:

• One conversation per control domain - Separate chats for Access Control (A.5), Cryptography (A.8), Physical Security (A.7), etc.
• One conversation per document - Analyze each policy or procedure in its own thread
• One conversation per audit area - Keep pre-audit prep separate from post-audit remediation

This approach also makes it easier to find specific discussions later.

Best Practices to Avoid This Error

For Consultants Managing Client Projects

• Create separate workspaces for each client
• Within each workspace, use separate conversations for different phases (gap analysis, implementation, audit prep)
• Export important findings to your own documentation regularly

For ISO 27001 Implementations

• Create one conversation per Annex A control category
• Generate policies in focused sessions rather than all at once
• Keep risk assessments in a separate conversation from control implementation

For Document Analysis

• Upload and analyze one policy at a time
• For gap analysis of multiple documents, create separate conversations for each
• Summarize findings from previous analyses rather than re-uploading files

Automatic compaction (Fast and Think)

How it works:

• Automatic summarization: When the thread approaches the route's threshold, older turns are compacted while recent detail is kept
• Visual indicator: You may see a brief "Compacting our conversation..." status during the process
• Continue in-thread: After a few seconds, the conversation resumes with key context preserved
• Beyond is different: Beyond runs assemble bounded context per step and do not use the same chat compaction path

Understanding token limits

Context window size depends on the route the product selected for that request (plan, mode, ADP), not on a user-picked model brand. The app may report limits around the low hundreds of thousands of tokens on some routes; numbers above are a practical order-of-magnitude guide, not a fixed Opus/Mistral menu.

What counts toward the limit:

• Every message you send
• Every AI response
• All uploaded file contents (text extracted from PDFs, spreadsheets, etc.)
• System prompts and framework knowledge

Getting Help

If you're consistently hitting this limit or need help recovering context from a very long conversation:

1. Contact support through User Menu → Help Center → Contact Support
2. Include the conversation title or workspace name
3. Explain what you were working on and what context you need to preserve
4. We can help you extract key information and structure your work into manageable conversations

Related Resources

• Known Issues - Token Limit Errors - Technical details and development status
• Troubleshooting Common Issues - Other chat and messaging errors
• Organizing Work with Workspaces - Best practices for managing multiple projects
• Uploading and Analyzing Files - File upload guidelines and limits