@coffax & @McFaul Thanks again for all the helpful feedback here.
We now have the following testing release:
that is expected to resolve the issue created as a result of this forum thread.
Hope that helps.