This is a known bug (also discussed in another forum thread); however, we are still waiting for the fix from @jensen-af.