> For the complete documentation index, see [llms.txt](https://docs.formsort.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.formsort.com/response-data-collection-and-management/variable-schema/orphaned-answers.md).

# Orphaned variables

A home for all your unresolved variable dependencies.

<figure><img src="https://1036686854-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MJPnL__mOdr_mLZ8nwf%2Fuploads%2FxndaY18aGQfrk9F1AzSu%2Fimage.png?alt=media&amp;token=757e3b51-e351-494b-a806-ece953f82224" alt=""><figcaption><p>An orphaned "dob" variable</p></figcaption></figure>

There are cases where an answer will no longer be collected within a flow, but it still has dependencies. For instance, you might delete a `date` question that collects a user's date of birth, however there is a [calculated variable](https://docs.formsort.com/response-data-collection-and-management/variable-schema/calculated-answers.md) function that requires that `date` input to calculate an age.&#x20;

In this case, the `date` answer will remain in the flow as an **orphaned** answer.&#x20;

{% hint style="info" %}
Generally, you don't want to have orphaned answers. We're working to make it harder and harder to generate them within flows.
{% endhint %}

## Resolving orphaned answers

### Re-use  variable&#x20;

<figure><img src="https://1036686854-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MJPnL__mOdr_mLZ8nwf%2Fuploads%2FYn5K6qCCEKhz7w97QNog%2Fimage.png?alt=media&amp;token=5a26b228-04db-4fc4-8d4a-8146167fdf29" alt=""><figcaption></figcaption></figure>

### Deleting orphaned variables

In order to delete an orphaned variable, you must remove it from any dependencies or "uses" it may have.&#x20;

Using the example at the top of this section, the `date` question that collects a dob would need to be removed as an input to the calculated variable that outputs an age.&#x20;

Once you see that **uses** are at 0, you will have the option to delete the variable.

<figure><img src="https://1036686854-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MJPnL__mOdr_mLZ8nwf%2Fuploads%2FCOrQC4XfgZI7p9PeJcib%2Fimage.png?alt=media&amp;token=52b50943-9391-452e-a1fd-fa139ff5c169" alt=""><figcaption></figcaption></figure>


---

# 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.formsort.com/response-data-collection-and-management/variable-schema/orphaned-answers.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.
