Hi,
We're an MSP and act as a Provider for a number of clients, primarily using it to integrate Incidents.
From time to time, something may happen to interrupt syncing with one or more of them and after it's restored, all the transactions queued up in RPS will go flooding out all at once. That in turn sometimes has unwanted consequences such as an incident that had been resolved getting re-opened.
Anyone have any recommendations on best way to handle that? The hope would to preserve the remote task connections if possible to preserve history and avoid duplicates, while minimizing out of order updates.
One idea is to delete all the queued transactions before service is restored, but don't know what kind of consequences that would have.
