> For the complete documentation index, see [llms.txt](https://help.bioinsight.illumina.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.bioinsight.illumina.com/connected-insights/resources-and-references/troub-overview.md).

# Troubleshooting

This section contains information on Connected Insights errors, issues, and corrective actions.\
For Connected Insights - Local software, this section also provides information on automatic and manual data backup.

## There is a configured pipeline in Data Upload for BioInsight Platform Core, but my analyses are not uploading

First check whether the particular subversion of the BioInsight Platform Core pipeline is supported in ICI, refer to [Supported Pipelines](/connected-insights/configure/configuration/du-introduction/du-supported-pipelines.md). Also note, when a new BioInsight Platform Core pipeline subversion is released your existing configurations will need to be updated to support them. Under the Data Upload section of the configuration, edit the relevant configuration (no additional actions are necessary) and save the configuration.

## The visualizations in my case aren't working anymore

If the following visualization files are deleted in BioInsight Platform Core it can impact the functionality of certain visualizations in ICI:

* coverageFiles: Coverage track
* ballelesFiles: B-allele track
* alignmentFiles: BAM track

Refer to [Supported Pipelines](/connected-insights/configure/configuration/du-introduction/du-supported-pipelines.md) for the files specific to a given pipeline.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.bioinsight.illumina.com/connected-insights/resources-and-references/troub-overview.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.