Ingested Knowledge – Ingestion Trail

Errors Detected in Record Received Step

Errors Detected in Record Submitted for Processing Step

Errors Detected in Content Pre-Check Step

Errors Detected in Content Unpacked Step

Errors Detected in Content Translated Step

Errors Detected in Content Broken Into Sections Step

This step can fail due to several reasons:

• Empty content: Files that contain only images or have no extractable text content
• File format issues: Unsupported file types, corrupted files, or files that exceed size limits
• Parsing errors: When the system can't properly extract or parse content from documents
• Text processing problems: Issues with chunking text that's too long, or errors during the chunking process
• gRPC message limits: If the snippetization response exceeds the 4MB gRPC message limit, it triggers a resource exhausted error
• Language detection failures: Problems identifying the document's language during processing
• Password-protected files: Documents that are secured and can't be accessed
• Third-party parser errors: Issues with external parsers used for PDFs and other file types that aren't properly normalized
• Processing timeouts: When the snippetization service takes too long to respond
• Invalid responses: Cases where the snippetization service returns malformed or empty responses

Errors Detected in Knowledge Article Sectioning Step

Errors Detected in User Information Processed Step

Errors Detected in Location Data Standardized Step

This step can fail due to several reasons:

• Missing or malformed location data: When geographic information in documents is incomplete, incorrectly formatted, or doesn't match expected patterns for normalization
• External geocoding service issues: If the system relies on external services to normalize location data, network connectivity problems or third-party service outages can cause failures
• Data processing errors: Issues with parsing location strings or converting them to standardized geographic formats
• Timeout errors: When geo-normalization takes too long to complete, it may timeout and fail
• System resource constraints: High processing loads can cause geo-normalization steps to fail due to insufficient system resources
• Invalid geographic references: Documents containing fictional locations, outdated place names, or ambiguous geographic references that can't be resolved to valid coordinates
• Configuration issues: Problems with geo-normalization service settings or missing required geographic databases

Errors Detected in Language Understanding Applied Step

Errors Detected in Content Enriched Step

Errors Detected in Processing Complete Step

Errors Detected in Record Prepared for Indexing Step

Errors Detected in Record Permissions Retrieved Step

Errors Detected in Permissions Unpacked Step

Errors Detected in Permissions Saved Step

Errors Detected in Permissions Indexed Step