Skip to main content

Troubleshooting Pipelines and Indexes

Diagnose and resolve common issues with pipelines and indexes.

Index Status: Partially Indexed​

  • Symptoms: All of the files were processed, but at least one of the files failed to be indexed.
  • Possible causes and solutions:
    • Missing dependencies: Ensure all required components and integrations are properly configured. If you're unsure about whether a component is correctly configured, you can run it in isolation to see if it works. For details, see Run Components and Pipelines in Builder.
    • Invalid YAML configuration: Check your pipeline YAML for syntax errors.
    • Corrupted files: Check if you your files are OK. You can use the get indexed files by status endpoint to see the status of the files.
    • Retry indexing: Reindex the failed files:
      1. Go to Indexes and click the index that you're troubleshooting. This opens the Index Details page.
      2. Under Files, click More Actions next to a failed file and choose Retry Indexing.

Index Performance Problems​

Symptoms: Indexing is slow or search results are poor.

Possible causes and solutions:

  • Document preprocessing: Optimize document splitting and cleaning strategies.
  • Embedding model choice: Consider choosing different embedding models for your content.
  • Index settings: Adjust document store settings for better performance.

Pipeline Performance Issues​

  • Symptoms: Your pipeline runs slowly or times out.
  • Possible causes and solutions:
    • Model latency: Try switching to a faster model or enable GPU acceleration. For details, see Enable GPU Acceleration for Pipelines.
    • Network bottlenecks: Check connectivity to external services and document stores.

Debugging Tools​

For details on how to debug your pipelines, see Debugging Pipelines.