# Additional Block Execution

Here is an example Graph that shows the order of execution.

<figure><img src="/files/e13ICs3hUf7FwbMg7Izr" alt=""><figcaption><p>Sample Graph (Click to enlarge)</p></figcaption></figure>

<figure><img src="/files/uTx4xa6ANsepj7Yf64bL" alt=""><figcaption><p>Connectors run first</p></figcaption></figure>

<figure><img src="/files/zifLh7oVEHOr113CeqrV" alt=""><figcaption><p>On Graph Start run second</p></figcaption></figure>

<figure><img src="/files/ErMMPXR4jsiF0fiaqIo7" alt=""><figcaption><p>TriggerAtStart option on a Timer will run third</p></figcaption></figure>

<figure><img src="/files/TUDyHvMAckxEdRWvQXyc" alt=""><figcaption><p>Finally, the Entry Point is executed</p></figcaption></figure>

<figure><img src="/files/Pi3EioImMyfoYsLzBE9t" alt=""><figcaption><p>Example showing when a timer will trigger with 'TriggerAtStart' set to false</p></figcaption></figure>

Finally, let's inspect the output from the Graph

<figure><img src="/files/pH1UTA30FiwHsQuvvWeN" alt=""><figcaption><p>Terminal output of the running Graph.</p></figcaption></figure>


---

# Agent Instructions: 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:

```
GET https://docs.graphlinq.io/dev-tooling/block-execution-order/additional-block-execution.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
