I called Customer Support regarding this. They are aware of the issue & have been working on it since May 28! No other details on workarounds or expected resolution.
