> For the complete documentation index, see [llms.txt](https://docs.enercalc.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.enercalc.com/efr-user-manual/calculation-types/working-with-beam-calculations/tributary-beams14/troubleshooting-tributary-dete.md).

# Troubleshooting Tributary Detection Issues

How to resolve common issues when a desired tributary beam is not automatically detected during calculation launch.

This section provides recommendations for resolving a number of common issues related to tributary beam detection.

1. Problem: Desired tributary beam is not automatically suggested during calculation launch.
2. Verify that the beam to be designed and the desired tributary element physically intersect with each other.

![](https://4249100372-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgHVzpA9PT0VcuNGp6j39%2Fuploads%2Fgit-blob-108d6d73109f779add5622825f6ba48399214d5c%2Fclip0135.png?alt=media)

1. Verify whether the desired tributary element was incidentally specified as a support during the previous approval step. Any element specified to act as a support for a beam is automatically disqualified from acting as a tributary element for that same beam. You can easily review supports specified in the previous step by clicking the “Supports” tab on the approval form. This will automatically highlight the approved supports by selecting them in the Revit view.

![](https://4249100372-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgHVzpA9PT0VcuNGp6j39%2Fuploads%2Fgit-blob-9aa939760e90cc8e8c5eac66282c0de5b27b7bd4%2Fclip0136.png?alt=media)

![](https://4249100372-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgHVzpA9PT0VcuNGp6j39%2Fuploads%2Fgit-blob-c34f801374c596dbc17b9f14968ad57b1bd29152%2Fclip0137.png?alt=media)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.enercalc.com/efr-user-manual/calculation-types/working-with-beam-calculations/tributary-beams14/troubleshooting-tributary-dete.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.