Hi Experts,
We are trying to use the new SAP PI Feature "Extended EOIO Error handling" for one of our Scenarios, in order to get an alternative handling for such messages which repeatedly fail during delivery, because if one of them goes in error in the dedicated queue, all the following will be in Status "holding".
So this Feature will be allowing the successor Messages to be automatically processed by moving/copying the erroneous message to another Queue (Error Queue) and give them either the Status canceled or delivered.
Problem: After applying this new functionality, we are getting Messages in Status Holding even if there was no message in error, and after checking the logs in details for the previous message in the related Queue (just before the first Holding message) we came to find that there was an error which has been automatically solved by the first PI retry. So the question is why These Messages (in Status holding) haven't been moved to the Error Queue in this case, or why haven't they been automatically processed after the precedent message (which was in error) was successfully delivered by an automatic PI retry.
Could anyone also please explain me the property "Error Queue Threshold" in this new Feature? (Maybe that would be the reason why the follwoing Messages were not moved to the Error queue, because I set it to 10).
Thanks in advance.
Best Regards,
Samir