We've identified this as a bug, and we'll roll out a fix in a future release. In the meantime, raise a new case and refer to this article for a temporary fix.
📌 Note: Please be aware that this temporary solution will only resolve the data at the time it is implemented. Until the bug is addressed, the data issue will continue to occur in the future.