Logs & Monitoring
The Logs page (/workspace/<slug>/logs) shows every event that flows through your automations: trigger fires in your database, which automations matched, and what actions ran. If you haven't deployed automations, there's nothing to log; this page matters once you have.
What gets logged
Every time a deployed trigger fires in your Supabase database, Skene adds a row with:
| Column | Description |
|---|---|
| Time | When the event was received |
| Source | Source table and schema (e.g., public.users) |
| Op | INSERT, UPDATE, or DELETE |
| Trigger | The database trigger(s) linked to the event |
| Dispatch | Which automations matched and what actions were taken |
Daily scheduled runs appear as separate rows with a Scheduled badge. For those rows, the Op column shows the cron step instead (Preflight, Action, Completed).
The page shows the last 7 days of activity (up to 500 rows per source), paginated at 50 entries per page, and updates in real time as new events land.
Reading log entries
Hover the Dispatch column to open the dispatch card with per-automation outcomes.
Dispatch phases
For each automation that could match an event, Skene evaluates four phases in order:
| Phase | What it checks | Possible outcomes |
|---|---|---|
| Precheck | The automation has an action type configured | Pass / Fail |
| Deterministic gate | Subject extraction, conditions (state), cooldown, max fires | Pass / Fail |
| Semantic matcher | LLM intent matching (fallback if gate fails) | Pass / Fail / Skip |
| Action | Tool selection and execution | Success / Fail / Skip |
An automation fires when the deterministic gate passes, or when the semantic matcher recovers a gate failure. Phases that don't apply to a given run (for example, the semantic matcher after the gate already passed) show as not applicable. The dispatch card shows which phase passed or failed and why.
Tool selection transparency
When an automation fires, Skene selects an action tool. The log shows:
- Path used: exact match (deterministic) or LLM-ranked
- Confidence score: how confident the matcher is (must exceed the automation's minimum threshold)
- Ranked candidates: top tool candidates with individual confidence scores
- Selected tool: which tool was chosen and the reason
Dispatch outcomes
Each automation in a log entry shows one of these outcomes:
| Outcome | Meaning |
|---|---|
| Success | The automation reached the action and it executed |
| Failed | The action ran and failed (hover to see why) |
| Skipped | The automation never reached the action (no action type, or the gate blocked it without recovery), or the action itself was skipped (e.g., no tool cleared the confidence threshold) |
Only Active automations enter dispatch. A paused or draft automation produces no dispatch entry at all: it won't show as Skipped, it just won't appear.
Debugging common issues
Event received but nothing matched
- Check that the automation status is Active (not Draft or Paused)
- Verify its trigger table and operation match the event source
- Check the deterministic gate. A cooldown or max fires limit may be blocking
Deterministic gate failed
- Subject not found: the entity ID column couldn't be resolved from the event payload. Check the automation's subject path configuration.
- State check failed: the entity is in the wrong lifecycle stage. Check stage assignments on the Journey page.
- Cooldown active: the automation fired recently for this entity. Wait for the cooldown to expire or adjust the cooldown period.
- Max fires reached: the automation has already fired the maximum number of times for this entity.
Semantic matcher failed
The semantic matcher is a fallback that uses LLM matching when deterministic resolution fails:
- Low confidence: the event payload doesn't closely match the automation's trigger and action descriptions. Improve the description text.
- Circuit open: too many recent failures caused the matcher to temporarily disable. It auto-recovers after 60 seconds.
Action failed
- Email delivery failure: check that Resend is configured and the recipient email is valid
- Webhook timeout: the target URL didn't respond within 10 seconds
- Tool not found: the configured action tool is disabled or doesn't exist
Agent activity
The Agent Activity page (/workspace/<slug>/agent-activity) shows a separate audit trail of runtime and engine activity, grouped by run:
- Automation fires and dispatch results, including tool matching decisions
- Daily scheduled run steps (preflight, action, completed)
- Engine events: compile, sync, journey generation
- Deploy actions: schema checks, trigger deploys and removals
It covers the last 30 days (the Logs page covers 7). Each entry links to the associated automation.
Next steps
- Automations: Configure automations and their conditions
- Supabase Integration: Trigger deployment and event flow details