Activity 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.

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

Symptom	Where to look
Agent gave a wrong answer	`retrieval` events — was the right chunk in context?
Agent hallucinated a price	`tool:` events — did it actually look the price up?
Agent didn’t transfer when it should	`turn:agent` reasoning + the `transfer_to_human` tool call.
Call ended abruptly	The last event — was it `disconnect`, `transfer-fail`, or a tool error?
Latency was high	Per-event latency column — usually a slow tool.

Filtering and search

The activity log 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.

Traces are retained for 90 days by default. Export to CSV or stream to your data warehouse via the API for longer retention.

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.

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.

Don’t paste raw traces into Slack or email. Use the export feature so the link expires and PII is masked.

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 agent activity

If you want to…	Go to
Debug runtime errors	Troubleshooting
Score a conversation in QA	Scorecards
Export traces to your warehouse	API Reference