@joelmearig Sorry, I’ll try to get this fixed as soon as possible. This was working fine before the latest update, right?