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

Debug with 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. Click Fix with AI next to any issue to open the AI assistant, which reasons through the fix and can apply it for you.

The Runs tab in the bottom panel lets you run your full pipeline or individual components, set breakpoints, and resume execution from a paused state.

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. Open your pipeline in Builder.

  2. Click Run Pipeline above the Input component and type a query in the Playground window that pops up.

    The Run option in Builder

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

  4. 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. Click Fix with AI to open the AI assistant, which reasons through the fix and can apply it for you.

    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.

Run a Pipeline with a Breakpoint​

A breakpoint pauses pipeline execution at a specific component so you can inspect the state of the pipeline at that point. After reviewing the captured snapshot, you can resume the pipeline from where it stopped or retry with modified inputs.

  1. Open your pipeline in Builder.
  2. Hover over the component where you want to pause execution and click the Run icon on the component card.
  3. Select Debug pipeline with breakpoint here from the menu.
  4. In the Runs panel at the bottom, fill in the pipeline inputs and click Run to breakpoint.
  5. Once the pipeline pauses at the breakpoint component, review the Traces and Outputs tabs in the Runs panel to inspect what each component produced up to that point.
  6. To continue from the breakpoint, click Resume pipeline. To retry from the same breakpoint with different snapshot inputs, click Modify snapshot and then Run with snapshot.
Run History

All runs in the current session are stored in the Runs panel history. Select any previous run from the history to review its inputs, outputs, and traces.

Run a Pipeline with Traces​

You can also run your full pipeline and inspect detailed traces for each component without setting a breakpoint.

  1. Open your pipeline in Builder.
  2. Click the Run button on the canvas toolbar.
  3. Select Debug with traces from the menu.
  4. Fill in the pipeline inputs in the Runs panel and click Run pipeline.
  5. Once the run completes, switch between the Traces and Outputs tabs to inspect the results.

Use the AI Assistant​

Builder includes a built-in AI assistant you can chat with to get help debugging your pipeline. Click AI Assistant in Builder to open the chat panel.

Describe what's going wrong, paste an error message, or ask the assistant to help you understand unexpected behavior. The assistant was designed with debugging in mind, but you can use it for other things too — like getting help with pipeline design or understanding how a component works.

The AI assistant runs as a streaming chat, so responses appear as they are generated. Each session keeps context across turns, so you can follow up on previous questions without repeating yourself.

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.