Learn about the new WorkflowRun event type and how to use them in your analytics.
WorkflowRun
across all customer-facing event logs. With this launch, you now have the ability to comprehensively track and analyze usage across all Glean AI products. These include Agents, which are the most frequently requested feature for these logs, AI Answers, Summarization, Deep Research, Daily Digests, and more.
This article explains what’s being introduced, what new metrics will be supported as part of this launch, and best practices for incorporating the new metrics in your analytics.
WorkflowRun
.
This log captures each top-level workflow invocation as a single, well-structured entry. It consolidates all relevant execution data in one place, enabling simpler, more reliable, and more performant analysis.
WorkflowRun
event includes:
Core Identifiers
runId
: Globally unique identifier for the top-level workflow invocationchatSessionId
and sessionTrackingToken
: Links to the user session contextExecution Context
feature
: Indicates the Assistant capability used (e.g., AI_ANSWER
, DAILY_DIGESTS
, AGENT
)initiator
: Source of execution (e.g., USER
, SYSTEM
, AUTOMATION
, EVAL
)platform
: Where the workflow originated (e.g., WEB
, REST_API
, etc.)Workflow Details
workflowExecutions
: Includes workflow-level IDs, namespaces (e.g., AGENT
or STATIC_WORKFLOW
), and execution statusstepExecutions
: Captures granular information about steps, status, errors, tools used, and citationsChat
, Workflow
, and WorkflowRun
logs to get complete metrics. After June 16, use WorkflowRun
exclusively.CHAT
: Base chat interactions (continues to exist)WORKFLOW
: Deprecated June 16, 2025 (April-June data only)WORKFLOW_RUN
: New comprehensive workflow tracking (June 16+ data)WorkflowRun
data.WorkflowRun
log type. This resource is designed to help you:
Date | Change |
---|---|
June 2025 | WorkflowRun logs deployed; Workflow logs replaced |
How can I analyze Agents usage with this new log type?
Will previous Workflow events appear in WorkflowRun?
WorkflowRun
. For April-June Assistant metrics, join across Chat
, Workflow
, and WorkflowRun
type.How do I identify user-triggered workflows vs. system/automated?
initiator = 'USER'
. The feature
, namespace
, or workflow_id
fields can further segment by workflow type.Some workflow_ids look like names, others are random strings—why?
Do I need to update my analytics pipelines/dashboards?
WorkflowRun
after June 16 and cover historic data as described above. See the Data Dictionary for transition queries and recommended field mappings.Where is the latest schema or field documentation?