I don't have a solution, but we are also experiencing the same across our instance. This started after the Unified Shell was implemented July 18, so seems like there could be a connection there. The WF instance URL was changed as part of this implementation, and that has caused a number of issues fo...