> 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/interpret-and-report/inter-variant-grid/avf-introduction/avf-flags-filter.md).

# Flags Filter

## Flags

Filters variants by the custom flags assigned to a variant defined in Test Components. For more information, refer to [Configuration](/connected-insights/configure/configuration.md).

## Artifact

Filters variants marked as an artifact. When a variant is marked as an artifact, any matching variants identified in future cases ingested with the same test definition will also be marked as an artifact. A match is considered when:

* For a small variant, the chromosome, position, reference allele, and alternate allele match.
* For an copy number variant, structural variant, or RNA splice variant of the same type, the reciprocal overlap exceeds 95%.
* For a translocation structural variant or RNA fusion variant, the involved genes match, if the impacted gene fusion is unidirectional then the matching variant must also be unidirectional, and the sqrt mean squared distance between the breakpoints must be less than 1700 bp.


---

# 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/interpret-and-report/inter-variant-grid/avf-introduction/avf-flags-filter.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.