AI Logs & Traces

When something goes wrong on a conversation, the trace tells you why. Omniflow keeps a structured log of every turn, every tool call, every retrieval, and every transfer — searchable, exportable, and tied to the customer transcript.

Everything lives in AI Logs, across every agent. Each agent used to have its own activity page as well; it showed the same run traces one agent at a time, so it has been removed and its links now open AI Logs.

What’s in a trace

A trace is a tree of events for one conversation:

Conversation #c_8a2f
├─ turn:user            "I need to change my flight"
├─ retrieval            5 chunks from "Booking changes" article
├─ turn:agent           "Sure — what's your booking reference?"
├─ turn:user            "PNR ABC123"
├─ tool:lookup_booking  args={pnr:"ABC123"} → ok (412ms)
├─ turn:agent           "Found it. What date works?"
├─ turn:user            "Friday"
├─ tool:rebook_flight   args={pnr:"ABC123",date:"2026-05-09"} → ok (1.2s)
└─ turn:agent           "Done — confirmation sent."

Every event has a timestamp, latency, model used, token counts (where applicable), and a link to the raw provider response.

Common things to look for

Filtering and search

AI Logs has a global search and a structured filter bar:

• By outcome — successful, transferred, escalated, dropped.
• By agent — narrow to a specific agent’s calls.
• By tool — find every conversation that hit lookup_booking.
• By keyword — search transcripts.
• By date / channel / language.
• By traffic — Real only, Tests only, or All traffic.

Test conversations

Testing an agent produces real conversations, and they are labelled so you can tell them from customer traffic:

Both open like any other log — transcript, sentiment, attachments — and both are excluded from QA scoring and never raise a ticket. The traffic filter defaults to Real only, so they stay out of the way until you go looking. Switch to Tests only straight after a test run to find yours.

The contact on a test conversation is the person who ran it, shown by name with their workspace role beneath — not their email address, which would read like a customer’s.

Replays

Click any conversation to open the replay — synchronized audio (for voice), transcript, and trace events on a single timeline. You can scrub, jump to a specific tool call, and play just the part that matters.

Sharing

Internal links are scoped to the workspace. To share a trace with engineering or a customer, use Export to generate a redacted, signed URL that expires in 24 hours. PII is masked automatically based on workspace settings.

Programmatic access

Every trace is also available via the API:

GET /api/v1/conversations/{id}/trace

See the API reference for parameters and the response schema.

Open in Omniflow

• Open AI Logs

Related