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, and who viewed Scout camera evidence).
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, table rows changing, custom fields being added, renamed or archived.
CRM	Ownership and assignment changes on deals and tasks, and each edit of a contact, company or deal field — your own custom fields included. Deals, companies and contacts created, notes added, and tasks created or completed by an automation, an agent or a connected AI (not yet those made on the page itself).
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.

Table rows are covered too. Editing a row in a table is recorded the same way, whoever did it — a person typing into the grid, an automation, an agent, or an integration writing through the API. Each entry keeps what the row said before the edit alongside what it says now, so “who changed this, and what did they change” has an answer for the procedures, policies and checklists your team keeps in tables. Bulk operations — a file import, or clearing a table — are recorded as one entry for the whole operation with the number of rows affected, rather than one entry per row.

So are charts and dashboards. Building a chart, changing what it measures, putting it on a dashboard, rearranging a board, deleting either one — all recorded, each entry keeping the full definition alongside it. This matters more here than almost anywhere else. A deleted chart or dashboard leaves nothing behind: there’s no archived copy to go back to the way there is for a table row, so the “before” held in the change entry is the only surviving record of what it was — which table the chart read, what it filtered on, which tiles sat on the board and where. “Who deleted our dashboard, and what was on it” now has an answer. What gets recorded is a genuine change, not a click: adding a chart that’s already on the board, or a save the editor rejects, changes nothing and so writes nothing.

And who looked. Opening a Scout photo is recorded as well — each time someone views a camera frame, whether on the page or by fetching the image itself, along with the device it came from. It’s the one thing here that isn’t a change: nothing was edited, but for a photo of a place or a person, who saw it is exactly the question asked later. Filter category → Access to see just those, alongside data exports.

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.

How far back it goes

The Logs page keeps its own record with its own lifetime, separate from your run-details retention period. Shortening one does not shorten the other: a run whose contents have been erased still appears here as an entry saying it happened, succeeded or failed, and when.

Where to go next

See an automation’s run history — when the question is about one agent, flow or Job rather than the whole workspace. No administrator access needed.
Set how long run details are kept — the separate clock on what a finished run recorded.
See what your AI is costing you — the AI lens has a cost column of its own on the AI Call Log.
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.
Chart a table and build a dashboard — build the charts and boards whose history the Changes lens keeps.
Access: who can do what — how administrator access is granted.