> For the complete documentation index, see [llms.txt](https://docs.elimity.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.elimity.com/reference-manual/v3.45.7/advanced-topics/broken-linking-strategies.md).

# Broken linking strategies

## What is a linking strategy?

Linking strategies allow connector admins to create relationships between multiple sources in Elimity Insights. Each strategy links entities of a single type in one source to entities of another type in a different source. Elimity Insights determines how to link these entities by comparing their attributes as specified in the linking strategy.

## Why do I see a warning about linking strategies referring to archived attribute types?

If at some point a linking strategy's attribute becomes archived, then Elimity Insights can no longer apply that strategy in a meaningful way. More specifically, the affected strategy will just continue using assignments for the archived attribute, which often result in no links at all. This behaviour may be unexpected, which is why connector admins will see warnings encouraging them to edit or remove the 'broken' linking strategies.


---

# 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://docs.elimity.com/reference-manual/v3.45.7/advanced-topics/broken-linking-strategies.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.