Event count processing race condition on showing camunda event counts

XMLWordPrintable

    • Type: Bug Report
    • Resolution: Done
    • Priority: L3 - Default
    • 3.3.0-alpha1, 3.3.0
    • Affects Version/s: None
    • Component/s: backend
    • None
    • Not defined

      Given:
      Event counts of camunda activity events have not yet been processed

      When:
      The event counts endpoint is called for this camunda process

      Then:
      a Http 500 is returned and the log contains:

      Response: {
  "errorCode" : "serverError",
  "errorMessage" : "An internal server error occurred.",
  "detailedMessage" : "Elasticsearch exception [type=index_not_found_exception, reason=no such index [optimize-event-sequence-count-invoice]]",
  "reportDefinition" : null
}

      Expected:
      The counts for these camunda activity events are just 0 or missing/null

            Assignee:
            Unassigned
            Reporter:
            Sebastian Bathke
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: