Hello Jitendra,
I believe the two decision steps are conflicting each other. By the time the change work item is triggered, the work item from the create branch will still be valid, because it is set as parallel to the change one. Each one is waiting for the other to be executed.
I'd suggest a change in the design, the decision from the change action should be placed after the end of the fork where the two branches meet. In this way, the work item from the creation branch will become obsolete and further cancelled. The user will have to approve just the change work item.
Regards,
Andres.
However there are circumstances when the code heavily relies on the workflow runtime context and you just unable to simulate the situation by autonomous testing.
