Has anyone gotten these? What are they related to, stack trace is not very verbose.
Requeuing the async job generally works.
One cause is if your prior scheduled replication of the same set has not yet finished.
David, thanks; that is what we posited it was, but we may save the history to confirm. Since we are not seeing incomplete replications, would it be safe to assume that it is essentially a duplicate scheduled async job?
I believe so. In our case, we replicate aggressively, every 15 minutes. When we some kind of transaction or load that affects a ton of data, we can see the replication take >15 minutes. The next scheduled trigger still fires, but is invalid because the prior one is still running. Then we requeue and all is well.
Would be nice if Infor did this automatically....
