Type something to search...
to navigateto selectESC to close

Longarm Logs and History

Back to longarm Docs

longarm separates request logs from batch-run history. Use Logs for low-level REST/MCP calls and Batch History for complete workflow runs.

Logs view

The Logs view records incoming REST and MCP activity with:

  • method
  • path
  • status code
  • timestamp
  • expandable request params
  • expandable result payload

REST requests appear with HTTP methods such as GET and POST. MCP tool calls are logged with method MCP and paths such as tools/call/open_app.

Retention and safety

  • retained logs remain visible even when the server is offline
  • sensitive token fields are redacted in logged params
  • newest entries appear first
  • the request log keeps up to 200 entries

Batch History view

Batch History records workflow runs rather than individual calls. Each run includes:

  • runId
  • status
  • progress
  • messages
  • captured screenshots

Use Batch History to inspect completed, failed, aborted, or still-running workflows. Screenshot steps store their results in the run history, and Plus users can export screenshot evidence.

Default batch history retention is 30 runs.