Thanks for the heads-up. The issue has been identified and resolved. It will be functioning as intended in the next update.
