Skip to main content

Troubleshooting Guide

Quick solutions for common issues in Captured Knowledge - emails, cases, ERP sync, and more

N
Written by Nick Laffey

Time required: 5-10 minutes (reference guide)

Prerequisites:

  • Access to Captured Knowledge

Expected results: After reviewing this guide, you will know how to resolve the most common issues with email linking, ERP integration, missing data, and action execution.

The error message just says "Building required" but you've already selected a property. The tenant is waiting for confirmation. Your ERP system shows the ticket exists but Captured Knowledge doesn't see it.

This guide gets you unstuck. Each problem includes why it happens and exactly how to fix it.

Issue Categories

Category

Frequency

Examples

Email Linking

Common

Wrong case assignment, thread issues

ERP Integration

Medium

Sync errors, ticket creation

Missing Data

Common

Building required, missing contacts

Action Execution

Rare

Permissions, system errors


Email Linked to Wrong Case

Problem: An email was automatically linked to Case A, but it actually belongs to Case B (or should create an entirely new case).

Why this happens:

  • AI matched based on property, contacts, and content similarity

  • Email thread was reused for a different issue

  • Similar properties or tenants caused confusion

  • Multiple issues mentioned in one email

Solution 1 - Move to Correct Case (if you know the right case):

  1. Open the case with the incorrectly linked email

  2. Find the "Import Email" action showing the email

  3. Click "Link to another case"

  4. Search for the correct case by case number, property address, tenant name, or problem description

  5. Select the correct case from search results

  6. Click "Confirm"

Solution 2 - Create a New Case (if you're not sure where it belongs):

  1. Open the case with the incorrectly linked email

  2. Find the "Import Email" action

  3. Click "Create new case"

  4. Provide instructions to help the AI (optional): "This is about Apartment 5C, not 5B" or "This is a new heating issue, not related to plumbing"

  5. Tick "Remove Link" for the current case

  6. Click "Confirm"

  7. Wait for processing to complete (10-30 seconds)

  8. Review the new case created by the AI

  9. Adjust the new case or manually link elsewhere if needed

Solution 3 - Unlink Completely:

  1. Open the case with the incorrectly linked email

  2. Find the "Import Email" action

  3. Click "Don't Link" or "Don't Link to Case"

  4. Optionally choose to move email back to inbox

  5. Confirm

Prevention: Review AI-suggested case links before accepting them. Check property and contact details carefully. When in doubt, use "Create new case" with specific instructions so the AI has the context it needs.

Note: You cannot create a new case from emails you created and sent from within Captured Knowledge.


Ticket Already Linked to Another Case

Problem: You want to link a case to a specific ERP ticket via the ERP Ticket tab, but the ticket is already linked to another case.

Why this happens:

  • A ticket can only be linked to exactly one case at a time

  • The ticket was previously linked to a different case

  • Duplicate cases may exist for the same issue

Solution 1 - Merge the Cases (best for duplicates):

  1. Move all messages from the secondary case to the primary case

  2. Link the ticket to the primary case

  3. Archive the secondary case once it contains no messages

Result: One consolidated case with complete communication history.

Solution 2 - Reassign the Ticket (Unlink & Relink):

  1. Open the original case

  2. Disconnect the ticket (Unlink)

  3. Open your current case

  4. Link the ticket to the current case

Result: The ticket is now linked to the correct case.

Solution 3 - Create a New Ticket (for new incidents):

  1. Create a separate, new ERP ticket for the current case

  2. Document that this is a new incident

Result: Each incident has its own ticket for clean documentation.

Prevention: Before linking, check if the ticket is already connected to an active case. Create separate tickets per incident for recurring problems.


Missing Real Estate Warning - "Building Required"

Problem: Error when creating ERP ticket or work order: "Building required" or "At least one building must be selected."

Why this happens:

  • ERP tickets and work orders must be associated with properties

  • Buildings weren't imported when the case was created

  • Properties were unlinked from the case

Solution 1 - Import from Case (if case has buildings):

  1. In the action form, find the Buildings section

  2. Click "Import buildings from case"

  3. Verify buildings appear and continue

Solution 2 - Manually Select Buildings:

  1. In the action form, open the property selector

  2. Search by building number, address, or city

  3. Select the building(s) and confirm

Solution 3 - Add to Case First:

  1. Exit the action form

  2. Edit the case to add buildings/properties

  3. Return to the action and use "Import buildings from case"

Prevention: Always verify case has buildings before creating ERP actions. Add buildings when creating a case if known.


Action Execution Failed

Problem: An action failed with an error message.

Common errors and solutions:

Error

Solution

"ERP ticket must exist before creating work order"

Create or link an ERP ticket on the case first. If the case already shows an ERP ticket and you still get this message, save the work order as a draft and execute it from the draft card.

"Building required"

See Missing Real Estate Warning above

"Invalid recipient email address"

Check "To" field for typos, verify format ([email protected])

"Failed to sync with ERP system"

Wait 1-2 minutes and retry. If persists, check if ERP system is accessible

"Title is required" or missing field

Fill all required fields (marked with *)

"You don't have permission"

Check with team administrator about your role/permissions

General troubleshooting:

  1. Read the error message carefully

  2. Check all required fields (red indicators show what's missing)

  3. Verify prerequisites (ERP ticket for work orders, buildings for tickets)

  4. Refresh the page if needed

  5. Contact support if the error persists after trying these fixes


Cannot Find an Entity

Problem: Search returns no results even though the entity exists.

Searching for Cases:

  • By case number: "1234" or "#1234"

  • By property: building name, unit, or address

  • By tenant name: full name, last name, or first name

  • By keyword: "faucet", "leak", "urgent"

  • Check filters: status, date range, team view

  • Try browsing: sort by date and scroll

Searching for Emails:

  • By subject: use partial text without special characters

  • By sender: email address or name

  • Check the correct tab: Inbound Emails vs Action Emails

  • Use date filters to narrow results

  • Check if email is linked to a case (won't show in global search)

Searching for Properties/Buildings:

  • Try different criteria: building number, unit, address, city, postal code

  • Use Quick Filters: "Residential Only" or "Buildings only"

  • Broaden search: remove filters, search by city first

  • Verify property exists in ERP system

  • Wait for sync if property was recently added to ERP

Searching for Service Providers:

  • Try partial names: "Quality" instead of "Quality Plumbing Services"

  • Check all smart groups: "From Case", "Previously used", "New to Building"

  • Verify trade selection matches the provider type

  • Check ERP system for correct spelling and active status

General tips: Start broad, then narrow. Use partial matches ("River" finds "Riverside Building"). Try different terms ("leak" vs "drip" vs "water issue"). Remove special characters. Check spelling carefully.


ERP Ticket Not Syncing

Problem: ERP ticket created in Captured Knowledge not appearing in ERP system (or vice versa).

Solution 1 - Wait and Verify:

  1. Wait 2-5 minutes for sync

  2. Refresh both ERP system and Captured Knowledge

  3. Check if ticket appears

Solution 2 - Check Ticket Details:

  1. Open the case in Captured Knowledge

  2. Go to ERP Ticket tab

  3. Look for the ticket number (e.g., "TK-5678")

  4. If you see "None" instead of a ticket number, creation may have failed

  5. Check the sync status (will show "Not Synced", "Sync Failed", etc.)

  6. Look for error messages

  7. Try unlinking and recreating the ticket

Solution 3 - Verify ERP Connection:

  1. Try creating a different ERP entity (work order, damage report)

  2. If those also fail, there's likely a connection issue

  3. Access ERP system directly to verify it's available

  4. Contact support if ERP is working but sync isn't

Solution 4 - Check for Duplicates:

  • Search in ERP by ticket number, property address, tenant name, or today's date

  • If found, link the existing ticket to the case in Captured Knowledge

Solution 5 - Manual Recreation:

  1. Create the ticket directly in ERP system

  2. Use "Link ERP Ticket" in Captured Knowledge to connect it

  3. Add a note explaining the manual creation

  4. Report the issue to support

Prevention: Fill all required fields before creating. Wait for success confirmation before navigating away. Verify ticket appears in ERP Ticket tab with proper number.


"Create New Case" Not Working

Problem: Clicked "Create new case" but nothing happens or no new case appears.

Solution 1 - Wait for Processing:

  1. Wait 30-60 seconds after clicking

  2. Don't navigate away

  3. Look for the processing spinner and the new case

  4. If nothing after 1 minute, refresh and check for new import actions

Solution 2 - Provide Better Instructions:

Instead of: (No instructions), "This is wrong", "Fix it"

Try: "This email is about Apartment 3B heating issue, not Apartment 4C plumbing", "Create a new case for this water leak - it's not related to the old heating repair", "This should link to ERP ticket #1234 about roof repairs"

Solution 3 - Check Unlinking Options:

  • Tick "Remove Link" for the cases the email should leave (most common)

  • Don't tick "Delete Case" unless certain

  • If you skip unlinking, the change may not have full effect

Solution 4 - Use Manual Linking Instead:

  • If you know where the email belongs, use "Link to another case"

  • Search for the correct case manually

  • Link directly without waiting for AI

Solution 5 - Report the Problem:

  1. Take a screenshot of the email and current state

  2. Note what you expected vs what happened

  3. Contact support with details


Other Common Issues

"I can't see my teammate's cases"

Problem: You cannot see cases that belong to your team members.

Solution: Check team filters and date range. Verify permissions with team administrator. Ensure you're in the correct team view.

"Attachments won't upload"

Problem: File upload fails or hangs.

Solution: Check file size (20MB limit per file). Try different file format. Verify internet connection. Split into multiple smaller files if needed.

"Changes aren't saving"

Problem: You make changes but they don't persist.

Solution: Click "Save" button explicitly. Wait for confirmation message. Check for validation errors in form. Refresh page to verify changes.

"I can't delete a case"

Problem: There's no delete option for cases.

Solution: Cases are archived, not deleted (preserves audit trail). Change status to Resolved or Rejected, then archive.


Getting Help

If these solutions don't work:

  1. Take a screenshot of the problem and any error messages

  2. Note the steps that led to the problem

  3. Record details: case number, entity IDs, what you tried, what happened

  4. Contact support at [email protected]

Include all the above information for fastest resolution.


Related Articles

Did this answer your question?