Digital Onboarding / data 141,488 events 10,000 cases in container

Data

One log, read once into this container from the mounted project directory. Every module and every job reads this one thing.

Events
141,488
Cases
10,000
Activities
21
Attributes
11
10 case / 1 event
What is in this log every figure a query - nothing here loads the log
First event01 Jan 2025 00:00
Last event29 Apr 2026 23:01
Span483 days
Events per case 1 to 19, median 17.0, mean 14.1
Objects10,000
Relations141,488
  case 10,000
Shortest case0.0 min
Median case27.0 min
90th percentile42.9 min
95th percentile48.6 min
Longest case74.3 min

Percentiles, not a standard deviation: case durations are right-skewed, so a deviation on one says less than it appears to. The unit is chosen from this log's own median.

Cases by number of events

1 to 19 events per case, counted exactly - event counts are small integers, so nothing is bucketed.

Shape over time bucketed by week, chosen from the span
Arrivals Completions Open cases

30 Dec to 27 Apr, 70 weeks. Arrivals and completions are counts within each week, so the gap between them is the net change during it. Open cases is the level, and is the backlog. Every week in the range is shown, including the empty ones.

Activities cases, not just events - an activity on many events but few cases repeats
Activity EventsShare CasesShare StartsEnds First seenLast seen
Validation 9,906 7.0% 9,906 99.1% 99.1% 1.6% 01 Jan 2025 00:00 29 Apr 2026 22:40
SMS Verification 9,243 6.5% 9,243 92.4% - 0.4% 01 Jan 2025 00:01 29 Apr 2026 22:41
Old ID Check 9,084 6.4% 9,084 90.8% - 0.5% 01 Jan 2025 00:03 29 Apr 2026 22:42
Product Selection 8,882 6.3% 8,882 88.8% - 0.1% 01 Jan 2025 00:06 29 Apr 2026 22:43
Company Information 8,829 6.2% 8,829 88.3% - 0.5% 01 Jan 2025 00:07 29 Apr 2026 22:44
Occupation Information 8,626 6.1% 8,626 86.3% - 0.2% 01 Jan 2025 00:10 29 Apr 2026 22:46
Transaction Information 8,563 6.1% 8,563 85.6% - 0.2% 01 Jan 2025 00:12 29 Apr 2026 22:47
Residency and Other Information 8,491 6.0% 8,491 84.9% - 0.1% 01 Jan 2025 00:13 29 Apr 2026 22:49
Person Registration 8,434 6.0% 8,434 84.3% - 0.8% 01 Jan 2025 00:15 29 Apr 2026 22:50
MRZ Read 8,147 5.8% 8,147 81.5% - 1.3% 01 Jan 2025 02:51 29 Apr 2026 22:51
Selfie Check 7,556 5.3% 7,556 75.6% - 0.2% 01 Jan 2025 02:52 29 Apr 2026 22:52
Video Call Start 7,486 5.3% 7,486 74.9% - 1.7% 01 Jan 2025 02:54 29 Apr 2026 22:54
NFC Read 6,746 4.8% 6,746 67.5% - 2.3% 01 Jan 2025 03:49 29 Apr 2026 22:55
Call Center Verify 5,797 4.1% 5,797 58.0% - 0.2% 01 Jan 2025 03:51 29 Apr 2026 22:56
One-Time Password Setup 5,703 4.0% 5,703 57.0% - 0.7% 01 Jan 2025 03:53 29 Apr 2026 22:58
Contract Sending 5,399 3.8% 5,399 54.0% - 0.1% 01 Jan 2025 03:54 29 Apr 2026 22:59
Application Completed 5,374 3.8% 5,374 53.7% - 8.4% 01 Jan 2025 03:56 29 Apr 2026 23:00
Mobile Activation 4,535 3.2% 4,535 45.4% - 45.4% 01 Jan 2025 03:57 29 Apr 2026 23:01
Abandoned Application 3,383 2.4% 3,383 33.8% 0.9% 33.8% 01 Jan 2025 00:18 29 Apr 2026 22:53
ID Front Side 1,171 0.8% 1,171 11.7% - 0.2% 01 Jan 2025 11:29 29 Apr 2026 06:50
Application Cancelled 133 0.1% 133 1.3% - 1.3% 04 Jan 2025 18:13 25 Apr 2026 16:44

Starts and ends are the share of all 10,000 cases that open or close with that activity. A dash means it never does.

Attributes case versus event decided by measurement, not declaration
AttributeLevelType DistinctMissing ExampleRange
Company Size Band case VARCHAR 4 - Small
Industry Sector case VARCHAR 6 - Construction
Company Age Years case DOUBLE 41 2,878 (2.0%) 9.0 0 to 40, median 7, p90 16
Annual Revenue Band case VARCHAR 4 1,422 (1.0%) 100K-1M
Channel case VARCHAR 3 - Web
Device OS case VARCHAR 4 - Windows
Customer Age Bracket case VARCHAR 4 - 30-45
Has Existing Relationship case BOOLEAN 2 - False
Requires Enhanced Due Diligence case BOOLEAN 2 - False
Region case VARCHAR 6 - Istanbul
Resource event VARCHAR 11 - SYSTEM

A dash under Missing means the attribute has a value on every event. A teal chip on the name is the enrichment layer that computed it.

Quality baseline generated on load not a button you had to find
CheckResultWhat it means
Events with no timestamp 0 A missing timestamp removes the event from every ordering.
Events with no activity name 0 Unnamed activities cannot be mapped.
Exact duplicate events 0 Same case, activity and timestamp - usually a double extract.
Single-event cases 255 A case with one event has no process to analyse.
Zero-duration cases 255 Start and end at the same instant - often a batch load artefact.
Timestamps at midnight exactly <0.1% Date-only timestamps make within-day ordering arbitrary.
Events sharing a timestamp inside a case 0 Their order within the case is arbitrary, so any path through them is.
Timestamp granularity sub-second Timestamps carry detail finer than a second, so their resolution is not what limits ordering.
Events out of recorded order 0 Recorded in a different order from their timestamps - one of the two is wrong, and the map believes the timestamps.
Timestamps in the future 0 A system default has landed in a real column, and it stretches the span.
Timestamps on a sentinel date 0 Dates a system writes when it means 'no date': 1970-01-01, 1900-01-01, 1899-12-30.
Time span 483 days 01 Jan 2025 to 29 Apr 2026
Cases not ending in a common end activity 1,243 Likely still running, or truncated by the extract window.
How an attribute was classified An attribute is a case attribute when it never varies inside a case. That is measured from the log on load, not read from a configuration file - which is why this screen works on any log you drop into the project directory.