Skip to main content

Hello everyone

I'm relatively new to building custom Celonis components in Studio and I've hit a wall with something that seems like it should be straightforward. Hoping some experienced folks here can point me in the right direction.

The issue: I'm trying to replicate the built-in throughput time explorer with a custom component, but I'm getting different results:

  • Built-in explorer: 12k cases (1-day filter)
  • My custom component: 13k cases (same filter)

What's confusing me:

  • I exported both results and compared them - all 12k cases from the built-in are in my results
  • My component has ~1k additional cases that seem valid when I check them manually
  • These "extra" cases definitely meet the 1-day criteria, so why does the built-in exclude them?

My current filter:

FILTER CALC_THROUGHPUT(
FIRST_OCCURRENCE '${start_activity}' ]
TO
FIRST_OCCURRENCE '${end_activity}' ],
REMAP_TIMESTAMPS("TABLE"."EVENTTIME", MILLISECONDS) )
/ 86400000.0 BETWEEN ${min_days} AND ${max_days};
 

Questions:

  • Did I make a mistake in my code that's causing this discrepancy?
  • Am I missing some implicit logic that the built-in explorer uses?
  • Any ideas what could cause valid cases to be excluded?

I've been stuck on this for days and would really appreciate any insights. Thanks!

Be the first to reply!

Reply