The Logs tab on the Automations page is scoped to one thing: automations. Workflows and SMS AI agents are separate engines and they do not appear there at all. That scoping is the single most common reason the logs look like they are lying to you.
What the Logs tab actually covers
- Open Integrations & Apps in the left navigation.
- On the Automations card, click Open.
- Click the Logs tab.
You get two views, switched from the toggle at the top right:
- Enrollments — one row per contact or deal that entered an automation.
- Step runs — one row per individual action an automation attempted.
Every row on both views comes from an automation. Nothing else writes to this page.
What is missing from it
Three engines can send a text, update a field, or start a conversation, and only one of them is represented here:
| Engine | Where it runs | Has a log page? |
|---|---|---|
| Automations | Integrations & Apps → Automations | Yes — this tab |
| Workflows and campaigns | AI Voice & Chat → Workflows and Campaigns | No |
| SMS AI agents | AI Voice & Chat → Agents | No |
Workflow enrollments, the individual texts a workflow sends, and AI agent conversations leave no rows on the Logs tab. Their record is the contact's timeline and the SMS thread itself.
The pattern that looks like a lie
Someone texts you. You open the Logs tab, and you see two rows at that exact second, both filtered_out, no steps run. Meanwhile you can see a real reply went out to that person at the same moment.
Both things are true. Two automations were offered the inbound text and correctly declined it, while a workflow — which does not log here — handed the thread to an AI agent and that agent replied. The empty-looking log is accurate for automations and silent about everything else.
The tell is on the contact's timeline, not on this page. See why so many timeline rows say System Automation.
What filtered_out means
filtered_out means the automation's audience filter did not match, so the record was never entered. It is not a failure and not an error, even though the status text repeats itself in the Error column of the same row.
Two things about that row read worse than they are:
- The Error column shows
filtered_outagain. That is the status restated, not a fault. Genuine failures show statusfailedwith a real reason. - The Steps column shows
0. In a Steps column a zero reads as "ran and did nothing". It means "never entered — skipped before step 1".
If you want to know why a filter did not match, open the automation in the builder, use Test on the Trigger step to pick that record, then open the Filter step and click Re-test filter. The result card there names the condition that failed and the value it saw. The Logs row does not carry that detail.
Where to look instead
| You are trying to find | Look here |
|---|---|
| Whether an automation entered a record, and what its steps did | Automations → Logs |
| Whether a text actually went out, and who sent it | The contact's Timeline |
| What an AI agent said and what the lead said back | The thread in Conversations |
| Whether a workflow enrolled or stopped for a contact | The contact's Timeline |
| Whether a workflow is still running for anyone | AI Voice & Chat → Workflows |
The timeline is the only surface that merges all three engines into one feed, which makes it the right starting point whenever the question is "did something happen at all" rather than "what did this specific automation do".
Related: read automation run logs and fix failed runs, use the contact timeline, and hand a cadence reply to an SMS AI agent.