This content has been marked as final. Show 4 replies
Try disabling the PO Output for communication program from the sysadmin responsibility.
Hope this helps,
Thats a good idea, but will the WF event get stuck at this point and end in error?
I don't think it will get stuck. Go ahead and try it in your test instance.
Thanks for the replies. In the end, end-dating "PO Output for Communication" did cause the WF to error on "Wait for Concurrent Program".
We found that we could just bypass the entire Email PO step in the workflow instead.