-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
False
-
-
False
-
-
Description of the problem:
In certain scenarios, after clicking abort, the data isn't reloaded right away and the state remains active. This can cause the user to press Abort again, and fail.
How reproducible:
50%
Steps to reproduce:
1. Run a workflow that takes time to complete
2. Click on Abort
Actual results:
Sometimes the state remains active for a few seconds
Expected results:
There should be some busy indication while abort is being executed, and the abort button should be disabled, once it's done, the instance should be reloaded immediately.