-
Bug Report
-
Resolution: Unresolved
-
L3 - Default
-
None
-
None
-
None
-
Not defined
Brief summary of the bug. What is it ? Where is it ?
When the min/max stats are calculated for a report, the incorrect default values of min 0 and max 0 are used if there are no instances within any of the processes included in the evaluation (at least one does not exist). A more correct behaviour would be to detect this scenario, and exclude that process from the query and the result set.
You can see this littering the log with the KPI scheduler service, for example: https://console.cloud.google.com/logs/query;query=resource.labels.container_name%3D%22optimize%22%0Aresource.labels.namespace_name%3D%223eff62a9-eb26-4af7-9973-76f5ae588239-zeebe%22;timeRange=P7D;summaryFields=:false:32:beginning;cursorTimestamp=2023-01-27T04:31:14.299185591Z?project=camunda-cloud-240911&pli=1
Testing Notes:
- Create a KPI report for a process that has no instances. Observe the logs
- Create a duration report that includes a process with no instances. Observe the results
- Create a report grouped by process instance duration. Observe the results
- Create a report grouped by user task duration. Observe the results
- Create a report grouped by flow node duration. Observe the results
This ticket was migrated to github: https://github.com/camunda/camunda-optimize/issues/10582. Please use this link for any future references and continue any discussion there.