Launching workflows creates zombie processes

opid30   3721481  0.0  0.0      0     0 ?        Z    Jul29   0:44 [bes-run-workflo] <defunct>
opid30   3731888  0.0  0.0      0     0 ?        Z    Jul29   0:42 [bes-run-workflo] <defunct>
opid30   3742045  0.0  0.0      0     0 ?        Z    Jul29   0:02 [bes-run-workflo] <defunct>
opid30   3742077  0.0  0.0      0     0 ?        Z    Jul29   0:02 [bes-run-workflo] <defunct>
opid30   3743428  0.0  0.0      0     0 ?        Z    Jul29   0:42 [bes-run-workflo] <defunct>
opid30   3751984  0.0  0.0      0     0 ?        Z    Jul29   0:42 [bes-run-workflo] <defunct>
opid30   3759958  0.0  0.0      0     0 ?        Z    Jul29   0:43 [bes-run-workflo] <defunct>
opid30   3771037  0.0  0.0      0     0 ?        Z    Jul29   0:42 [bes-run-workflo] <defunct>
opid30   3782674  0.0  0.0      0     0 ?        Z    Jul29   0:44 [bes-run-workflo] <defunct>
opid30   3792844  0.0  0.0      0     0 ?        Z    Jul29   0:48 [bes-run-workflo] <defunct>
opid30   3796011  0.0  0.0      0     0 ?        Z    Jul29   0:02 [bes-run-workflo] <defunct>
opid30   3796295  0.0  0.0      0     0 ?        Z    Jul29   0:03 [bes-run-workflo] <defunct>

The presence of processes marked as <defunct> indicates that they are zombie processes. Zombie processes
occur when a child process has completed execution, but its parent process hasn't yet read its exit status.
These processes don't consume system resources like memory or CPU, but they do occupy an entry in the process table.