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

In Cockpit, I can see the id of the activity that failed a job

    XMLWordPrintable

Details

    • Feature Request
    • Resolution: Fixed
    • L3 - Default
    • 7.13.0, 7.13.0-alpha3
    • None
    • engine, webapp
    • None

    Description

      AT

      I can see the id of the activity that failed a job in the runtime view and in job logs in the history view (new attribute introduced with CAM-10378).

      For these entities:

      • the failed job log
      • the runtime job
      • the runtime incident
      • the historic incident

      mgm-controller-panel

        This is the controller panel for Smart Panels app

        Attachments

          Issue Links

            depends on

            Feature Request - A new feature of the product, which has yet to be developed. CAM-10378 Accurately show the failed activity in cockpit

            • L3 - Default - Minor issue or issue with existing workaround, feature requests and questions
            • Closed
            is related to

            Bug Report - A problem which impairs or prevents the functions of the product. CAM-11605 failedActivityId is NULL when loading Job Log in the History View

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

            Feature Request - A new feature of the product, which has yet to be developed. CAM-11404 In Cockpit, highlight the failing activity for incidents

            • L3 - Default - Minor issue or issue with existing workaround, feature requests and questions
            • Open
            links to

            Web Link https://github.com/camunda/camunda-bpm-platform/issues/2366

            Web Link https://github.com/camunda/camunda-bpm-platform/issues/2373

            Activity

              People

                martin.stamm Martin Stamm
                tobias.metzke Tobias Metzke-Bernstein
                Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  Salesforce