Handling duplicate data/timestamps from misbehaving 3rd party OPC UA server?

Hello all, I'm working on a project where one of the data sources to our Ignition 8.1 gateway/historian is a 3rd party OPC UA server that we do not own or control - and unfortunately, we have been receiving duplicate data+timestamps from this server which have ended up quarantined by the Store & Forward system.

We're working with our partners on the project to attempt to have the 3rd party OPC UA server's behavior corrected, but in the meantime are also looking at potential work-arounds to avoid our quarantine getting filled up with garbage in case the issue remains unresolved (there are concerns about missing other items in the quarantine that may legitimately require attention).

Has anyone else run into an issue like this? It looks like there's no way to automate handling of data after it hits quarantine, so we're considering workarounds like having the 3rd party OPC UA server populate its values to non-historized tags on our gateway, then have a gateway script that transfers those non-historized tags to our actual historized tags (possibly also checking timestamps or values for validity in the process)... Most of what we've thought of so far involves added complexity and uncertainty though, so if there are any "known good" solutions established for handling/filtering unreliable external data I'd love to hear about them. Thanks in advance!