Sorry for the delayed response, @mattmcd. It looks like our support team is working on your ticket. In the meantime, another developer reported a similar problem and was resolve their issue. Can you check to see if the same scenario is happening on your end? Here is the post for your reference.