Type of Error | Action | Notification Type | Retry |
---|---|---|---|
Source Stream is down | The process is not invoked. | No Notification | Once Source Stream is up, the poller picks up the messages on the stream run. |
Technical or Remote (CCB or Target Stream is unreachable) | Message is published to Source Stream (Rolling back the messages) | Email (optional) | Poller picks up the messages on the next run. Note: Inactivate this integration process until all applications (CCB, Stream) are up to avoid the continuous reprocessing of messages that would fail. |
Type of Error | Action | Notification Type | Retry |
---|---|---|---|
NMS DB down/unavailable | Executes Select/Update to table MYC_CSS_PARAM_VIO_TEXT from NMS DB | Email | Restart programmed schedule once the issue is resolved. |
Technical or Remote (Source OCI Stream is unreachable) | The only error scenarios expected are technical errors while accessing OCI Stream, such as: password expired, certificates expired. The expectation of OCI Stream API call is rare programmed schedule must be paused. | Email | Once fixed OCI Stream connectivity restart scheduled integration. |
Technical or Remote (OIC API Connection is unreachable) | This will have an impact as integration will not have a chance to trigger another batch of data and will wait until next schedule run. | Email | Once fixed OCI Stream connectivity restart scheduled integration. |
NMS Parse data from String to XML | This is a rare scenario since standard xpath function is used parseXML() to parse string to XML format, MYC_CSS_PARAM_VIO_TEXT is updated with CSS_NOTIFIED='E'. | Email | From NMS Flag from CSS_NOTIFIED needs to be updated from 'E' to 'N' to be reprocessed. |
Convert XML format to JSON format | This is a rare scenario since it uses standard mapping. MYC_CSS_PARAM_VIO_TEXT is updated with CSS_NOTIFIED='E'. | Email | From NMS Flag from CSS_NOTIFIED needs to be updated from 'E' to 'N' to be reprocessed. |
Type of Error | Action | Notification Type | Retry |
---|---|---|---|
400 or 500 error status when CCB Create Customer Contact API is invoked | As part of the CED/Pending file processing, in the message collection, each errored record or message is captured. After reaching the max error count, an email with the details of the failed records is sent. | Email is sent with errored details for each CED/Pending file type. Also, in the global fault handler, an error email notification is sent if the notification flag is turned on. | Reprocessing happens on the next schedule job process. |
Not 400 or 500 error status when CCB Create Customer Contact API is invoked but other status code except 200. For example: 403, 401 error code | The integration process will be stopped, and no further messages will be processed from the file. | In global error handler scope, an email notification will be sent if notify error flag is turn on. | To retry (for example: 401) passwords expired, does not make sense, hence should not be retried in this scenario. After fixing the expired password, the flow can be scheduled again. |
Oracle Responsys SFTP server being down/unreachable | The integration will not pick any files for further processing. | In global error handler scope, an email notification will be sent if notify error flag is turn on. | Reschedule the parent process in integration process (Oracle Utilities Responsys CED Process). |
Type of Error | Action | Notification Type | Retry |
---|---|---|---|
Oracle Utilities Responsys CCB Cust Contact Create integration service is unavailable | API call will be failed and CED file will be processed. The process is terminated. | In global error handler scope, an email notification will be sent if notify error flag is turn on. | Reschedule the integration process. |
Type of Error | Action | Notification Type | Retry |
---|---|---|---|
Responsys SFTP server being down/unreachable. | The integration will put back the consumed message in OCI stream. | In global error handler scope, an email notification will be sent if notify error flag is turn on. | OCI message will be consumed automatically on next schedule run. |
OCI stream down/unreachable | Email is sent. | In global error handler scope, an email notification will be sent if notify error flag is turn on. | OCI message will be consumed automatically on next schedule run. |
Type of Error | Action | Notification Type | Retry |
---|---|---|---|
Not 401 or 500 error status when Responsys API is invoked | Error messages from each invoke in a batch for a particular Oracle Responsys instance, along with account ID, template name and delivery channel is collected in a collection. | A separate email is sent for errors in each Oracle Responsys instance. | These notification messages cannot be recovered. |
Error status that is 500 or 401 when Responsys API is invoked | Error messages from each invoke in a batch for a particular Oracle Responsys instance, along with account ID, template name and delivery channel is collected in a collection. | A separate email is sent with error collection of each Responsys instance. | These notification messages are republished back to TargetNotificationStream, until the issue is resolved. Note: If the resolution takes a while, inactivate the process to avoid receiving emails and republishing. |
Technical or Remote (TargetNotificationStream OCI Stream is unreachable) | During polling, if the OCI Stream is unreachable, the OIC instance is not instantiated. | Email (optional) | Poller will pick up the messages on next try. |
Invalid delivery channel or Oracle Responsys instance | Error messages from each invoke in a batch for a particular Oracle Responsys instance, along with account ID, template name and delivery channel is collected in a collection. | An email is sent with the error collection for each batch. | These notification messages cannot be recovered. |
Type of Error | Action | Notification Type | Retry |
---|---|---|---|
Technical or Remote (Target Stream is unreachable) | • Fault is logged in the OIC Instance. • Fault is rethrown to Global handler. | No Notification | CCB must resend the notification outbound message to OIC. |
Any Global | Fault is rethrown back to CCB. | Email (Optional) | CCB must resend the notification outbound message to OIC. |
Type of Error | Action | Notification Type | Retry |
---|---|---|---|
Business Error when processing records in file | The errors are collected in an error collection and the processing continues. | An email notification is sent when error count reaches the max.error.count defined in the configuration lookup. | Based on the errors in the error notification email any updates to the record is done manually. |
Technical or Remote (CCB or SFTP location is unreachable) | Global fault is thrown | Email (optional) | Reschedule the process once the issue is resolved. |
Type of Error | Action | Notification Type | Retry |
---|---|---|---|
Source Stream (CCB) is down | Email notification (if configured) | On Error, run the integration again. | |
Technical or Remote fault | Email notification (if configured) | On Error, run the integration again. | |
OCI Rest call to create/modify DVM api | Email notification (if configured) | On Error, run the integration again. |