ProductDevelopersPartners
OverviewOya UniversityOAgentsAgent IDEKnowledgeAgent BrainChatEvalsChannelsRoutinesRun HistoryMonitoringOrganizationsWidgetBilling
Docs›Run History

Run History

Browse every run your OAgent has executed: inputs, outputs, source, status, timing, and the full replayable execution trace. It is both your production audit trail and the artifact you hand a customer who asks what the agent did.

Tip
This is the artifact you show your customer. When a client asks why the agent did something, you hand them the exact run: every value it read, every tool call, every output, replayable step by step. Not a summary you reconstruct after the fact, and not something anyone else in this category can give you.

Overview

Every time your OAgent processes a message, from chat, a gateway, or a webhook, it creates a run. The Runs page gives you a complete audit trail of what went in, what came out, and whether it succeeded, making it essential for debugging and monitoring production OAgents.

Access it at /agents/{agentId}/runs via the Runs link on any OAgent card.

Runs page with filter bar and expandable run cards
Browse all agent runs with filters and expandable details.

Run Cards

Each run is displayed as an expandable card showing:

  • Source: Where the run originated (Chat, Gateway, Webhook)
  • Status indicator: Green dot for success, red dot for error
  • Timestamp: When the run executed
  • Input: The message or payload that triggered the run
  • Output: The OAgent's response

Click a card to expand it and see the full input and output. JSON payloads are automatically formatted for readability.

Tip
Expanded cards show the complete input and output, useful for debugging gateway and webhook integrations.

Open a run to see its full execution trace: the interactive DAG trace viewer shows every step the OAgent took, including skill calls and their inputs and outputs.

Filtering

The filter bar at the top lets you narrow runs by source and status:

  • Source filter: All / Chat / Gateway / Webhook
  • Status filter: All / Success / Error
  • Search: Full-text search across input and output content
Tip
Combine filters to quickly find problematic runs. For example, filter by Gateway + Error to find failed platform messages.

Status Indicators

Each run card shows a colored status dot:

  • Green dot: The run completed successfully
  • Red dot: The run encountered an error

Error runs include the error message in the expanded output, helping you diagnose issues without switching to logs.