See what happened — the Logs page

When something looks off — a table went empty, an email didn’t send, a device dropped offline at 2 p.m. — the first question is always the same: what actually happened, and when? The Logs page answers it. It’s a single, searchable record of everything your workspace did: every automation run, every AI call, every setting an admin changed, every Scout device event. No digging through separate screens — one home, one place to look.

Where to find it

Go to Settings → Logs. If you had the old Activity log bookmarked (it used to live under Settings → System), that link still works — it now opens the Changes lens described below.

Pick a lens for what you’re looking for

The page opens on a set of tabs. Each tab — a lens — is just the same log filtered down to one kind of activity, so you jump straight to the part you care about:

Lens	What it shows
Timeline	Everything, newest first — events and changes together. The “what broke at 2 p.m.?” view.
Changes	Who changed what, and when — the workspace audit trail (settings edits, deletes, access changes).
AI	Every AI model call — which model, whether it succeeded, how long it took.
Memory	Documents and things added, updated, or annotated in Memory.
Scouts	What your Scout devices saw and did.
Runs	Automation and agent runs starting, finishing, or failing.
Ingest	Inbound email, bank transactions, and other data arriving.
Automations	Checklist and reminder signals.
CRM	Ownership and assignment changes on deals and tasks.
System	Internal and sign-in-related events.

The lens tabs are driven by what your workspace actually records, so the exact set you see reflects the features you use.

Start with the Timeline

The Timeline is the incident view. It weaves two kinds of records into one feed, newest first:

Events — things that happened: a run finished, a device came online, an email arrived.
Changes — things someone or something did on purpose: an admin edited a setting, an automation deleted rows.

A Source column tells the two apart at a glance, and the When / Actor / Entity / Details columns tell you the rest — who or what was responsible, what it touched, and a plain-language summary.

Because an incident is almost always “recently”, the Timeline is scoped to a time window — use the Window control to switch between the last hour, 24 hours, 7 days, 30 days, or all time. It defaults to the last 24 hours.

Worked example — an email didn’t go out. A customer says they never got their invoice. Open Logs → Timeline, set the window to Last 24 hours, and scan for the run: you see the automation started, the AI drafted the message, and then a red failed send with the reason right there in the Details column — the mail provider rejected the address. No guessing, no reproducing it: the record already says what went wrong and when.

Answer “who changed this?” with the Changes lens

When the question is about a setting — who turned this off, who deleted those rows — switch to the Changes lens. It’s the workspace audit trail: every configuration edit, delete, restore, and access change, attributed to the person or automation that did it. Deletes done by an automation are attributed to that automation, so you can always tell a person’s action from a flow’s.

Use the filter dropdowns to narrow by actor, area, action, or category — for example, everything a specific teammate changed, or every delete this week.

Export a filtered slice

Every lens has an Export button in its toolbar. It downloads exactly what’s on screen — the export respects whatever filters and window you’ve set — in CSV, Excel (XLSX), or JSON. Reach for it when you need a record outside Routario: a spreadsheet for a monthly review, or a JSON feed for a security team’s monitoring tools.

Where to go next

Running & debugging a flow — when the thing you’re investigating is one specific automation run.
Working with data: tables & imports — undo a bad delete after the Logs page tells you what happened.
Access: who can do what — how administrator access is granted.