Well this didn't take long. Hopefully tech support will start getting a list of known issues moving forward to help prevent this sort of thing moving forward. Very nice email from Nick.

Hi Dave - Nick Blasier here, Support Manager. Our engineering team has reviewed the issue and logged it as a known issue now. Due to the age of the development and the availability of a workaround, we likely won't be able to research and fix this one in the short term. Apologies for all the back and forth to get here! As we grow in size and offerings, we're working on ways to make known issues like these more readily available to our customers - hoping to make this kind of information easier to come by next time around. Watch for us to grow our knowledge base and documentation over the next year.

Thanks for reporting this! Let us know if there's anything else we can do to help here.

Nick