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

Fix wrong pagesize value in ProcessInstanceFetcher

    XMLWordPrintable

Details

    • Bug Report
    • Status: Done
    • L3 - Default
    • Resolution: Done
    • None
    • 2.3.0-alpha2, 2.3.0
    • backend
    • 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.

      mgm-controller-panel

        This is the controller panel for Smart Panels app

        Attachments

          Issue Links

            is related to

            Task - A task that needs to be done. OPT-1253 Reduce Code Duplication in EngineImportMediators

            • L3 - Default - Minor issue or issue with existing workaround, feature requests and questions
            • Done

            Activity

              People

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

                Dates

                  Created:
                  Updated:
                  Resolved:

                  Salesforce