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

REST API: Misleading error messages

XMLWordPrintable

    • Icon: Bug Report Bug Report
    • Resolution: Won't Fix
    • Icon: L3 - Default L3 - Default
    • None
    • None
    • engine

      Catching ProcessEngineException in the REST API and interpreting it as a single error cause that may not be correct is a bad pattern. Users may be mislead to the wrong cause of an error.

      Example: https://github.com/camunda/camunda-bpm-platform/blob/7.8.0/engine-rest/engine-rest/src/main/java/org/camunda/bpm/engine/rest/sub/history/impl/HistoricProcessInstanceResourceImpl.java#L56

      Check all REST API resources for this anti-pattern.

      Related forum post: https://forum.camunda.org/t/historic-process-instance-does-not-exist-rest-request-exception/5591

        This is the controller panel for Smart Panels app

            [CAM-8631] REST API: Misleading error messages

            Thorben Lindhauer created issue -
            Roman Smirnov made changes -
            Component/s New: engine [ 11656 ]
            Thorben Lindhauer made changes -
            Workflow Original: camunda BPM [ 45047 ] New: Backup_camunda BPM [ 56396 ]

            Thorben Lindhauer added a comment -

            We are closing this ticket as part of our backlog grooming. Reasons:

            • We did not receive sufficient evidence that this ticket is important

            Thorben Lindhauer added a comment - We are closing this ticket as part of our backlog grooming. Reasons: We did not receive sufficient evidence that this ticket is important
            Thorben Lindhauer made changes -
            Resolution New: Won't Fix [ 2 ]
            Status Original: Open [ 1 ] New: Closed [ 6 ]

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

                Created:
                Updated:
                Resolved: