Process Explorer
Process Explorer groups captured activity into ordered paths for a selected population. Use it to inspect repeated sequences, alternate variants, and observed delays. The result is evidence from the selected scope, not a complete model of the business or a prescribed workflow.
Concepts that change the result
- Case lens chooses what counts as one case, such as a record, base transaction, session, or source session.
- Activity lens chooses the event naming and granularity, such as event type, event class, table plus event type, or event text.
- Session grouping combines nearby events into one session; the session gap determines when inactivity starts a new session.
- Variant is one repeated ordered activity sequence across the selected cases. Its count describes that selected evidence, not how common the sequence is in the business as a whole.
Time range, tables, sources, case lens, activity lens, and session grouping all define the evidence being summarized. The same captured history can therefore produce different paths under different settings, and results should not be compared as if those settings were unchanged.
Interpretation limits
- Confidence describes how strongly the selected evidence supports the displayed repeated path. It is not business approval, causal proof, or a guarantee that the path is complete.
- Edge counts show how often a transition appeared in the selected evidence. They indicate frequency, not why the transition happened.
- Self-loops show an activity returning to itself. They represent repeated captured occurrences and are not automatically noise or a separate workflow step.
- Median delay is the middle observed delay between activities in the selected traces. A long median is a place to investigate, not proof of a bottleneck or its cause; it can include waiting, work outside the observed scope, incomplete capture, or grouping choices that combine unrelated work.
Only captured activity inside the selected time range, tables, sources, and grouping is represented. Work outside that scope or capture window is absent, so the explorer cannot establish a complete workflow, intent, ownership, or causality from event order alone.
For source-level evidence behind a displayed path, open the relevant records in Activity. That evidence can clarify what was captured, but it does not fill gaps in the selected scope or prove why an event occurred.