Uploaded image for project: 'camunda BPM'
  1. camunda BPM
  2. CAM-10672

Link historic incidents to the specific stacktrace source

XMLWordPrintable

    • Icon: Bug Report Bug Report
    • Resolution: Fixed
    • Icon: L3 - Default L3 - Default
    • 7.12.0, 7.12.0-alpha4
    • None
    • engine
    • None

      Historic incidents are linked to their respective source by CONFIGURATION_ and INCIDENT_TYPE_.

      • In case of job incidents, this source is a runtime job which might not be accessible anymore when the respective process instance ends. The stacktrace is not accessible anymore by then as well.
      • In case of external task failures, the source is an external task who is only linked to the last known errorDetail which might change in every retry. The stacktrace of previous retries is not accessible anymore and all incidents show the same errorDetail.

      AT
      The historic incidents are linked to the specific source of the stacktrace which is accessible at any time.

      Hint
      The job log and the external task log both link to such durable sources and are able to show the correct stacktrace regardless of the instance's status.

        This is the controller panel for Smart Panels app

              Unassigned Unassigned
              thorben.lindhauer Thorben Lindhauer
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: