Bogus SQL Server (XTP) in-memory error 41842 claiming 4B rows updated

We run a large, very active set of in-memory (schema-only) tables - the main table has been split (sharded) into 5 separate databases because the table is a total size of > 50gb (Standard Edition limits the total size of in-memory tables to 32gb per database). The largest of the databases contains a 10gb table with roughly 1.5M rows. The tables take 10K or so updates per minute, each of which updates between 500-10K rows. Tables are read from ~1K times per minute, returning between 50 and 1K rows. Anonymized Schema: Indexes: There are 4 of these servers. About once a week, one of the servers stops accepting updates and instead returns this message (error Msg 41842): "Too many rows inserted or updated in this transaction. You can insert or update at most 4,294,967,294 rows in memory-optimized tables in a single transaction." That's just not a possible number, so we appear to be hitting some other condition that is triggering this message. When it happens, the server rejects all data changes and we have to reboot and refill the schema-only tables. Servers are running on 12 CPUs w 128G memory (125G for sql) Microsoft SQL Server 2019 (RTM-CU11) (KB5003249) - 15.0.4138.2 (X64) May 27 2021 17:34:14 Copyright (C) 2019 Microsoft Corporation Standard Edition (64-bit) on Windows Server 2016 Standard 10.0 (Build 14393: ) (Hypervisor) Has anyone else seen this error?