Error Handling
Where ever possible, the SEPA DD CSM has automated error handling to either resolve issues itself or pass control back to the calling flow with details of the problem. There are, however, a few situations where this is not possible due to the severity and level of the error. This page outlines those situations and how the CSM will handle them.
Errors within the Bulker
The Bulker is a core aspect of IPF, it is configured and deployed with the CSM, but is a separate component. Any errors occurring in the Bulker will be due to technical issues, not data quality issues, since all payments are checked before being submitted to the Bulker. If the Bulker reports an error when a transaction is submitted, the CSM will raise a system event of type 'ERROR'. This event will contain the whole transaction in the payload of the message. The offending Transaction will be removed from the message currently being handled by the CSM, and processing will continue. In doing so, the CSM hands responsibility of the transaction to the client’s support team, as it is unable to pass it to the scheme itself. If there is only one transaction in a message, or all transactions are removed due to errors, the SEPA flow transitions to submission rejected.
Errors within the Debulker
If the input file is successfully debulked and all components are ready, the Debulker will notify the SEPA DD CSM. In case of failure, (e.g., duplicate file, corrupt file), a system event of type ERROR will be raised and a notification will be sent by the SEPA DD CSM Scheme Pack. No downstream processing will be triggered in such cases.
| It will be the responsibility of the client’s support team to fix the issue and re-trigger the debulking process. |