I have below issue in my production environment, can someone please help resolving the same.
In below screenshot,
Step “S1” is completed and Step “S3” still executing (Without error). in this case, S1 is completed first and it should wait at gateway step “S4” for S3 since it is parallel gateway… but instead of waiting , gateway step S4 is considering S3 path as dead path and moving to status 768 which is unsatisfied join.
IS Version 9.5
Step Properties are attached
Fix level: IS_9.5_SP1_Core_Fix8
I could have helped sure shot, from the screen, it worth trying out, change S4 gateway from parallel to complex and then change Join Type value to “AND”, it should work. Parallel gateway step is designed to spawn out multiple threads outwards but not inwards. give a shot and share your results.
but we are using similar gateway steps in many places and we have not experienced such issues there. as per SAG documentation parallel gateway will work with both inward and outward flows.
and when we check the “ignore dead path” property, issue was disappeared but SAG’s recommendation is to uncheck that property.
Strange Sreekanth, I felt this can help my team and tried to simulate, it was working properly without checking Ignore dead path notification at process. May be typical wM issue
we are having the same issue in 10.1 version also(occurring on both Parallel and Complex Gateways with AND join type ). what is the relevant fix for 10.1 version.
