Troubleshoot Custom Components

Learn how to fix the most common issues with custom components.

Troubleshooting Upload Issues

These are the issues that occur when component is ingested into deepset Cloud but before it's installed.

  • If you're uploading through REST API or commands, you get an error response that will guide you through the steps to fix the issue.
  • If you're uploading by releasing the forked repository, go to the Actions tab of your repository and check the actions that failed.

Troubleshooting Installation Issues

These are the issues after the component is ingested into deepset Cloud and deepset Cloud attempts to install it.

Symptoms

Your component is not visible in the Pipeline Builder's component library.

Actions

  1. Refresh the Pipeline Builder page and wait a couple of minutes for the installation to complete.
  2. If your component is still not visible, print the installation logs of the latest version of your custom components to check the issues that occurred:
    1. On Linux and macOS, run: hatch run dc:logs.
    2. On Windows, run: hatch run dc:logs-windows.

Troubleshooting Operational Issues

These are the issues that may occur when a component was correctly uploaded and is visible in Pipeline Builder, but fails to work correctly in a pipeline.

Symptoms

Your component doesn't work in your pipeline.

Actions

Check the pipeline logs for issues and remedy actions:

  1. Go to Pipelines and click the pipeline whose logs you want to see.

  2. Click Logs on the Pipeline Details page to view all information messages, warnings, and errors your pipeline produced.

    Pipeline details page with the Logs tab highlighted