Thank you for your post. This issue is a known defect that we are working to resolve in a future build. We do have a workaround that is documented in the below document.
We hope to have this out sooner rather than later, but as with any bug, there is no ETA for a resolution.
It seems to be inconsistent, because I just pushed the to 120 machines, and they're all coming back Finished...