Troubleshoot Pipelines and Indexes

Diagnose and resolve common issues with pipelines and indexes.

---

Pipeline Issues

When creating or updating a pipeline, you may see validation errors that prevent deployment. Here are common errors and how to resolve them.

Unconnected Model Provider

Symptoms: The Issues panel in Pipeline Builder shows a model connection issue for an LLM or Agent component.

What happens: When a component such as LLM or Agent is configured to use a model provider that isn't connected to Haystack Enterprise Platform, an issue appears in the Issues panel. The issue shows the name of the affected model and provider.

Solution:

1. Open your pipeline in Pipeline Builder.
2. Click Issues to open the Issues panel.
3. Find the model connection issue and click Connect next to it.
4. Enter your API key and any other required details for the provider.
5. Click Connect to save the integration.

The issue disappears once the provider is connected. For general information on connecting model providers, see Connect to Model and Service Providers.

Invalid Streaming Component Error

If your pipeline contains components that don't support streaming, this error is shown:

Error message: "Invalid streaming component - This pipeline contains a component that does not support streaming. Remove or replace the incompatible component to enable streaming."

Solution: To resolve this error:

1. Identify which components in your pipeline don't support streaming.
2. Either remove the incompatible component or replace it with a streaming-compatible alternative.
3. For more information about streaming and compatible components, see Enable Streaming.

Pipeline Stuck in Deploying

Symptoms: The pipeline status shows deploying for an extended period of time and does not change.

What happens: The platform automatically detects pipelines that have been deploying longer than expected and marks them as failed to deploy. This usually happens within a few minutes. Once the status changes to failed to deploy, you can redeploy the pipeline.

Solution:

1. Wait a few minutes for the platform to detect the stuck deployment and update the status to failed to deploy.
2. Once the status has changed, redeploy the pipeline. For details, see Deploy a Pipeline.
3. If the pipeline fails to deploy again, check the pipeline YAML for configuration errors.

Pipeline Performance Issues

Symptoms: Pipeline is slow 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.

Index Issues

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.

Indexing Performance Issues

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.

Debugging Tools

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