Hi Jamboss1, sorry about that! The issue is fixed and we found the underlying cause, so it shouldn't happen on future releases.