Skip to main content
For the complete documentation index for agents and LLMs, see llms.txt.

Debug with Pipeline Builder

Fix your pipeline issues. Submit a query and examine the detailed component logs to understand how the component processed it to produce the final result.

About This Task​

You can debug your pipeline by checking the component logs for each run. You can also use the Issues panel to see all validation and runtime issues in one place. Click Inspect next to any issue to jump directly to the affected component or connection and fix it.

Check Component Logs​

You can inspect each component's logs per run to understand how the component processed the input and produced the output.

  1. In Haystack Enterprise Platform, go to Pipelines.

  2. Click More Actions next to the pipeline you want to debug and choose Edit.

    The edit pipeline option

  3. In Pipeline Builder, click Run and type a query in the Playground window that pops up.

    The Run option in Pipeline Builder

  4. Wait until you get an answer and minimize the Playground window using the down arrow.

  5. Check the components in your pipeline. There is a Logs tag on the components whose logs you can view. Click View on a component to see its output logs.

    The debug icon on a component card
    Check the Issues Panel

    After running the pipeline, you can also open the Issues tab at the bottom of Builder to see all runtime errors in one place. Click Inspect next to any issue to jump directly to the affected component.

    Component Logs

    Component logs are automatically available for all components in your pipeline when debugging. This includes intermediate processing steps and outputs from each component, helping you trace how data flows through your pipeline.

Example​

This image shows how to inspect component logs in Pipeline Builder:

Run a pipeline in Builder and inspect component logs created for the run.

Debug Single Components​

Run individual components to verify their settings, input and output, and check if they work as expected. For information on how it works, see Run Components in Isolation.