We’re currently evaluating this issue for a fix in a future release.