Pre-Qualification Failed Handler
Like the Plan Item Failed handler, there is no default implementation of the Pre-Qualification Failed handler provided with the product.
Be aware that the Pre-qualification failed handler deals with errors raised not only in Feasibility, but also, Automated Order Plan Development. Even if in your architecture you don’t have a Feasibility step, you have Automated Order Plan Development, and if Automated Order Plan Development raises exceptions, Orchestrator publishes an event to the Pre-Qualification Failed handler and wait for a response. If there is no Pre-Qualification Failed handler implemented, nothing further happens for that order and it is “stuck”.
Even if Automated Order Plan Development exceptions are expected to be rare for your application (i.e. you validate the order thoroughly prior to Automated Order Plan Development), consider at the very least, implementing monitoring on the Pre-Qualification Failed request queue, so that operations is aware that Automated Order Plan Development has failed for an order, and some action needs to be taken to move the order on.
You might want to consider making the Pre-Qualification Failed handler “just another” source of Technical Exceptions. In this way, a framework for dealing with automating Technical Exception handling, could be used to also deal with Pre-Qualification Failed requests. This is the approach that is described in the next section.