I hope someone can shed some light on this.
We are facing an issue with default engine behavior regarding retries.
We have a driver that connects to different target systems. When a
system is unreachable, a retry status is issued which retries the same
event after a configurable time. So far, so good.
However, this retry blocks the driver completely until it is processed.
When events for one of the other target systems occur, they sit in the
queue until the first system is reachable again. Which maybe never.
What options do we have to place an event at the back of the queue
again? We have external options like the workorder driver, but the
preference is to have no external dependencies.
i d f o c u s
Identity | Access | Security