Open flow logs
Open the Akış Logları (Flow Logs) panel from the editor toolbar; it lists that flow’s recent runs. Click one row to read its node trace.
The Akış Logları panel shows the recent runs of a single flow. It lives inside the editor, it is not the Flow İzleme screen in the left menu, and it closes when you leave the editor. The list holds the last 50 runs. Click a row and you get the triggering message, the step-by-step node trace and the final variables.
Before you start
- A Flow Builder item in the left menu; the item is hidden when your plan lacks the feature.
- A flow opened in the editor: double-click its row in the list, or use the pencil button.
- A flow that has run at least once; with no runs the panel says Henüz log yok.
Step by step
These screens sit inside the Intent AI section. Sign in, open Intent AI; the menu names below are in that section's left menu.
Open the flow in the editor
Open Flow Builder from the left menu. Double-click the row of your flow. The editor opens with the toolbar across the top.
Open the Akış Logları panel
Click the Akış Logları button on the toolbar. The panel opens on the left and its header carries the total run count. Click the run you want; each row shows the date, a status badge and a masked phone number.
Read the steps in the node trace
Find the Tetikleyen mesaj and Node izleme headings in the detail view. Read the Gelen and Giden lines of each step in order. A failed run adds a red Hata box at the bottom.
Result checkIf it did not work
Check these
- Henüz log yok means the flow has never run. Check that the toolbar shows the flow as Aktif and that the Başlangıç node has a line selected.
- On [INV-AT-041] Log listesi yüklenemedi, press the Yenile button in the panel header. Send that code to support if the error stays.
- The panel has no date or status filter and stops at the last 50 runs. An older run you are looking for cannot be opened here.
Does this step look different in your panel?
We can review the screen and exact error text together.
This guide was checked against the product UI and code inventory on 29 August 2026.
