Fix wrong pagesize value in ProcessInstanceFetcher

XMLWordPrintable

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

      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.

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

              Created:
              Updated:
              Resolved: