> For the complete documentation index, see [llms.txt](https://docs.flopsar.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flopsar.com/4.0/method-execution-tree.md).

# Method Execution Tree

## Terminology

Throughout the entire documentation, we use some terminology regarding the execution of methods. The picture below presents a single method execution tree. The first element of the tree is called ***Entry Point***. All the methods' calls, down the execution chain, are called ***Invocations***. The entire structure is called ***Execution Tree***.

![Execution Tree](/files/-MTuSePEN8ePQFkw5zIT)

An entire execution tree is completed and built on the server. When some invocation comes to the server, and the corresponding execution tree, it is part of, cannot be found, a new tree is created. The entry point of this tree is then called ***Incomplete Entry Point***. When the entry point is completed, then its execution tree is stored in the database.

## Execution Tree Structure

The picture below depicts the procedure of how the execution tree is built. In the picture below you can see four, sample execution trees of some method *A* call.

![](/files/-Ly9HbvOvi6WCxIFp61N)

The first `a` view shows how the real execution stack looks. This is a real execution flow that takes place in your application. The second `b` view presents the same stack instrumented by your agent. Depending on your configuration, the instrumentation may not cover the entire stack. The empty, grey boxes represent missed, not instrumented methods. As you can see, at this very point your instrumented execution flow is not complete. Moreover, in your application runtime, there can be situations when some of the instrumented method calls will not be reported. The empty, red boxes in the third `c` view represent this situation. Finally, what you actually observe in the workstation is the last `d` view. This view presents an assembled stack with missing calls ignored. Now you know how to interpret the execution stack in the workstation and why the resulting stack can differ from the original one.


---

# 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.flopsar.com/4.0/method-execution-tree.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.