> For the complete documentation index, see [llms.txt](https://docs.buildings.ability.abb/collection/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.buildings.ability.abb/collection/english-v14/documentation/engineering/skript-engine/python-skripte-schreiben/output-logging-und-fehlerbehandlung.md).

# Output logging and error handling

## Overview

When executing scripts in the Eliona system, all outputs, such as `print`-statements, information about execution, and errors, in the **Grafana container (SSR)** are logged. Each script execution receives a unique **Function ID**, which makes it possible to specifically track the outputs of individual scripts. This guide explains what such log entries can look like and what they mean.

## Important notes

### Immediate output with `print`-statements

To ensure that `print`-outputs are visible immediately, use in your `print`-statements the parameter **`flush=True`**. This prevents the output from remaining in the buffer and ensures that it appears directly in the log.

**Example:**

```python
print("Result: 42", flush=True)
```

### Error logging

All errors that occur during the execution of a script are also displayed in the Grafana log. With appropriate error handling, you can ensure that additional details are logged, which makes troubleshooting easier.

**Example of error logging:**

```python
try:
    # Code that could cause an error
except Exception as e:
    print(f"An error occurred: {e}", flush=True)
    raise
```

By using `flush=True` in combination with comprehensive error handling, you can ensure that all important information is immediately visible in the log and that potential problems can be identified and resolved quickly.


---

# 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.buildings.ability.abb/collection/english-v14/documentation/engineering/skript-engine/python-skripte-schreiben/output-logging-und-fehlerbehandlung.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.