# Troubleshooting errors

[As you already know](/kb/appmixer-studio-features/implementing-logic.md), Appmixer allows you to implement logic that makes your flows smarter, but also more complicated. In both cases, you probably won't avoid errors. Luckily, we got you covered with a feature called "Logs" that allows you to see the past flow runtime and detect the bottlenecks of your flows.

{% embed url="<https://youtu.be/lSpM2v0vfVA>" %}
How to troubleshoot errors using Logs?
{% endembed %}

"Logs" is a powerful feature that helps you investigate the details of past flow runtimes and troubleshoot errors. There are multiple ways to view Logs.

### 1. View Logs in a flow

To view Logs in a flow, open the flow and click on the little icon in the panel below.

![View Logs in a flow](/files/-MfD3kCD0fjT-PhHkVIL)

{% hint style="info" %}
Note that you can view logs for both active and inactive flows. In other words, you don't have to stop the flow to view logs.
{% endhint %}

### 2. View Logs in Insights

Alternatively, you can use our Insights features and view Logs there.

![View Logs in the Insights tab](/files/-MfD5Hhan46Jracy85wC)

You can, of course, view the log detail. Simply click on the log you'd like to check in better detail and wait for the window to show up.

![View Log detail](/files/-MfD68i7oqUiwrKXtqNM)

Viewing Logs may be pretty simple once you know where to click. There is, nonetheless, some terminology that remains to be explained.

{% tabs %}
{% tab title="Log terminology" %}
**Status**\
Status indicates whether or not the flow needs your attention. There are two types: Successful and Error.

**Source Component**\
The component from which the data was sent.

**Target Component**\
The component to which the data was sent.

**Port Name**\
The name of either the input port where data was received or the name of the output port the data was sent to (see Port Type to make the difference). Note that even though many components contain only one input and one output port, there are many components that may contain more input or output ports. Therefore, the port name allows you to differentiate between the ports.

**Port Type**\
Either "in" for an input type of port or "out" for an output type of port.

**Timestamp**\
The time at which the log was tracked.

**Message**\
A full details of the message.

**Error**\
In case of an error, this field contains more information about the error.
{% endtab %}
{% endtabs %}

Logs is a great feature that allows you to double-check if you've set up your flow correctly. Should you encounter errors, logs help you identify the problematic points.

[N](/kb/appmixer-studio-features/visual-features/selecting-multiple-objects.md)ext, you'll learn about some of the visual features that help you work more efficiently. Stay tuned. 😎


---

# 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.appmixer.com/kb/appmixer-studio-features/troubleshooting-errors.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.