Hi @boston85719,
Thanks for reaching out about this. This appears to be related to a known issue—please see our post here for more details:
Thanks, Will