Mixed up order in processing of JobStateChanged events #937
Description
Describe the bug
It can be observed that events for state changes are processed within the module way after the state has already proceeded beyond the one the event belongs to.
It leads for example to calls to the job scheduler for jobs reporting they are running now, while they have actually already been fully processed and are completed.
To Reproduce
To further investigate start any application, include the process engine and set a breakpoint with the following condition eventArgs.CurrentState.Classification < eventArgs.JobData.State.Classification in here
Expected behaviour
While this is behaviour is accepted and expected outside of the module, this is an issue inside. We expect events to be processed in order within the module