Hi @LMTraina99! Sorry this took awhile to get back to you. The development team did some testing of your issue and discovered that this is indeed a bug that needs to be fixed. Thanks for bringing this to our attention!
(For your reference, internal bug #OM-43590)