To repair this situation, you could potentially close the resultWorkerErr channel following writing to it. Such as, you might incorporate the following line of code after the line that sends the error around the channel: The obstacle Here's that there's an obvious solution, which happens