Skip to main content
Use log history in Fetch Hive when you want to review individual prompt, workflow, chat Agent, Hive Agent, or knowledge base runs and inspect what happened during a request.

​
Overview

Fetch Hive gives you separate log views for prompts, workflows, chat Agents, Hive Agents, and knowledge base processing. Each view starts with a table of runs, then lets you open a detail sheet for deeper trace and run-level inspection. For the Hive Agent-specific walkthrough, see Hive Agent Logs.

​
How do I open logs for prompts, workflows, agents, or Hive Agents?

Open one of these sections in the main sidebar:
  • Prompts
  • Workflows
  • Agents
  • Hive Agents
  • Knowledge Bases
Then click Logs in the secondary navigation. Prompt, workflow, chat Agent, and Hive Agent logs expose a Source section in the secondary navigation. Hive Agent logs use a workspace-wide run table and let you switch between All Sources, Dashboard, and API runs. If you already have a full request ID, paste the req_... value into global search and choose Go to request.

​
How do I filter logs?

These log pages use the date-range control, pagination, and column visibility controls in the table. Each log page also has its own filter set:
  • Prompts logs support Provider, Model, API keys, and Prompt
  • Workflows logs support API keys, Workflow, source navigation, and Delivery
  • Agents logs support Provider, Model, API keys, and source navigation
  • Hive Agents logs support Hive Agent, Status, source navigation, and text search by Hive Agent name, objective, or request ID
  • Knowledge Base logs support Knowledge Base, API keys, and Type

​
What’s tracked

Depending on the resource type, Fetch Hive shows combinations of completion time, resource name, provider, model, tool usage, objective, node count, source count, status, total cost, total tokens, duration, API key, collaborator, and request ID. Hive Agent logs show Hive Agent, Objective, Status, Pass, Nodes, Sources, Total Tokens, Total Cost, Duration, API Key, and Collaborator.

​
How do I read a run detail sheet?

Click a row in the logs table to open the matching detail sheet. The sheet starts with a header, a status, and a summary strip. The detail panel can include response content, request details, inputs, metadata, output sections, trace spans, and run-specific fields.

​
Traces

When a run has a trace, Fetch Hive shows a waterfall panel on the left side of the detail sheet. Use this panel to move through the run step by step. Selecting a span updates the detail panel so you can inspect that span’s timing, input, output, metadata, cost, tokens, or tool details. Hive Agent traces show source preparation, planning, execution, verification, repeat decisions, budget checks, retryable stage errors, and final completion or cancellation. Run-level failure messages stay on the overview and terminal spans, allowed budget checks stay informational, and planner, executor, and verifier stages can expand to show child AgentRun reasoning, LLM responses, and tool panels inline. When a Hive Agent is cancelled with a partial result, the run remains cancelled but keeps verified node output in the run details.

​
Notes

  • The trace waterfall appears when trace data is available.
  • You can also open these same detail sheets from Users after drilling into a tracked end user.
  • For Hive Agent status meanings and node details, see Hive Agent Logs.