It's here for a reason :)

And didn't we already conclude that this was not an issue? It's an issue due to another bug in WF