Details
-
Bug
-
Resolution: Fixed
-
Neutral
-
5.3.8
-
-
Empty show more show less
-
Sprint 5 (Basel)
-
1
Description
In AbstractCommandAction we don't deal with potential SchedulerExceptions, which are typically left uncaught, as they occur in another thread.
This happens e.g. if the scheduler cannot instantiate the CommandJob (missing parameter candidate)
As a result, the job is not executing at the time the action checks for it, and considers it done and successful.
Checklists
Acceptance criteria
Attachments
Issue Links
- relates to
-
MGNLUI-3510 Clean up async action execution
-
- Closed
-