# Where can creators inspect automation activity?

Canonical: https://uvilno.com/answers/where-to-inspect-automation-logs
Updated: 2026-10-27

Open App Data in Uvilno's builder and select Automations & Logs. The view shows installed rules and committed event metadata with bounded refresh. It does not expose project source or private record bodies, and an activity entry does not prove an external service was executed.

Start with the rule definition: its collection, triggering operation and supported actions. Then perform one identifiable write and locate the corresponding event. If the transaction fails, inspect the visible error rather than expecting a successful activity entry for an uncommitted operation.

Logs are a diagnostic view, not a customer database export. They intentionally avoid sensitive record bodies. Website rollback does not rewind application data, so record changes and version changes should be reviewed separately when debugging a production workflow.

## What to verify

| Check | Published behavior | Verification |
| --- | --- | --- |
| Installed rules | The tab lists rules in the saved schema. | Compare collection and action names with the planned workflow. |
| Activity | Events represent committed database operations. | Trigger a disposable write and refresh the tab. |
| Privacy | Activity metadata excludes full customer record bodies. | Use Records for authorized row inspection instead. |

## Steps

1. Open App Data, then Automations & Logs.
2. Create one disposable record through the app.
3. Compare the resulting row with the actual event metadata.

## Editable starting brief

Plan a private issue tracker with issues and activity_logs collections. Add a declared activity rule for issue creation and wire the interface to real Uvilno.db operations. Include a concise owner verification checklist for App Data and Automations & Logs, while keeping private record bodies out of event messages.

## Sources

- [Uvilno public SDK documentation](https://uvilno.com/docs)