Skip to content

StopTask flags a failed process as stopped #369

Closed

Description

@njoubert-cleverage

Regression of 5.5 (#337).

StopTask (stop) flags the process history as stopped (setStopped()) even when it is already failed. In 5.4.1 it called setFailed(), so a failed process stayed failed.

Example: the initialization of a task fails, the process goes on (deprecated behaviour) and the history is failed; a stop task reached afterwards turns it into stopped: the Process <code> stopped log is written at the success_level, ProcessEvent::isProcessStopped() is true and the UI shows the execution as stopped instead of failed.

Fix: do not flag a failed history as stopped.

Found during the audit after the 5.5 release (audit-v4-post-release.md #220).

Activity

  1. added a commit that references this issue on Oct 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions