> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.moveworks.com/agent-studio/development-and-testing/logs/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.moveworks.com/_mcp/server.

# Logs

# Log Viewer

1. Go to [https://my.moveworks.com/](https://my.moveworks.com/) and log in
2. Click the App Switcher in the top right
3. Click on the "Logs" tile in the home page

![](https://files.readme.io/8965ecd65e8190bccc3fa16e69ee1ed317d26badc13cd5576bdc4a196bf7fd56-image.png)

## Filters

![](https://files.readme.io/352b0bf2e62a9877a5be10bfa94d8d46eaf979478c367a496a535921aca05397-image.png)

1. **Time-range** - This filters for logs between a lower and upper time bound. It defaults to the last 6 hours and can go back a maximum of 14 days. Log timestamps indicate approximately when related activity occurred, so use the time range to locate relevant logs rather than to establish the exact time an event occurred or profile latency.
2. **Root UUID** - This UUID that ties an entire Plugin execution together.
3. **Requestor** - This is the user email of the user who triggered the Plugin.
4. **Log Level** - This is the level of the log.
   1. By default it will be **LOG\_LEVEL\_DEBUG**.
   2. If an error occurred, it will be **LOG\_LEVEL\_ERROR**.
5. **Log Type** - This can be **compound\_action.trigger**, **compound\_action.step.execute**, **action.http.trigger**
6. **Response Code** - This is only applicable to **action.http** logs. It filters these logs based on the requests response code (e.g. 200, 404)

## Docs

- [Log Type Reference](https://docs.moveworks.com/agent-studio/development-and-testing/logs/log-type-reference.md): 
- [Log Data Security](https://docs.moveworks.com/agent-studio/development-and-testing/logs/log-redaction.md):