Uploaded image for project: 'Camunda Optimize'
  1. Camunda Optimize
  2. OPT-1621

Fix wrong pagesize value in ProcessInstanceFetcher

    XMLWordPrintable

    Details

    • Type: Bug Report
    • Status: Done
    • Priority: L3 - Default
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 2.3.0, 2.3.0-alpha2
    • Component/s: backend
    • Labels:
      None

      Description

      Finished & RunningProcessInstanceFetcher use the max page config value for activityInstances instead of processInstances.

      AT:

      • Finished & RunningProcessInstanceFetcher use getEngineImportProcessInstanceMaxPageSize

      Note:
      While fixing this a more severe bug in the import was uncovered and fixed:
      For the edge-case that there were no nextPage results but results for the exact previous timestamp, the import was not done for the entities returned by the exact timestamp query.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              sebastian.bathke Sebastian Bathke
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: