Error Handling and Email Notifications
Error Handling
This section describes the different ways errors are handled in the integration:
- Summary of Integration Error Handling
- Resubmitting the Error Instances in Oracle Integration Cloud
Summary of Integration Error Handling
Note: Error emails are sent according to the configured notification flags
Integration Process: OU OPOWER CCS Affordability File Transfer
Use the following table to recover from affordability transfer failures. It relates each fault to processing actions, email notifications, and restart instructions:
Type of Error | Action | Notification Type | Retry |
|---|---|---|---|
Technical Fault |
|
| Correct the source connection issue. Run the OIC process manually or wait for the next scheduled run to retrieve eligible files. |
Technical Fault |
|
| Activate the common OIC flow. Run the OIC process manually or wait for the next scheduled run to retrieve eligible files. |
Partial Processing |
|
| Run the OIC process manually or wait for the next scheduled run to continue from the saved filename. Do not rename the source files. |
Business Fault | N/A | N/A | N/A |
Integration Process: OU OPOWER CCS Sent Customer Communication Sync
The following table relates SENT synchronization faults to notifications and recovery steps. Partial-processing recovery retains the interval and resumes from the affected page:
Type of Error | Action | Notification Type | Retry |
|---|---|---|---|
Technical Fault |
|
| Correct the connection issue. Run the OIC process manually or wait for the next scheduled run. |
Business Fault |
| Business Error Email | Correct the query parameters, mapping, or application data. Run the OIC process manually or wait for the next scheduled run. |
Partial Processing |
| Business Error Email | Run the OIC process manually or wait for the next scheduled run to process communications starting from the page that errored up to the current datetime. |
Integration Process: OU OPOWER CCS Push Customer Communication Sync
The following table relates PUSH synchronization faults to notifications and recovery steps. Partial-processing recovery retains the interval and resumes from the affected page:
Type of Error | Action | Notification Type | Retry |
|---|---|---|---|
Technical Fault |
|
| Correct the connection issue. Run the OIC process manually or wait for the next scheduled run. |
Business Fault |
| Business Error Email | Correct the query parameters, mapping, or application data. Run the OIC process manually or wait for the next scheduled run. |
Partial Processing |
| Business Error Email | Run the OIC process manually or wait for the next scheduled run to process communications starting from the page that errored up to the current datetime. |
Integration Process: OU CCS OPOWER Account Communications Get
The following table shows how account communication requests return faults to Customer Cloud Service and what to correct before resending a request:
Type of Error | Action | Notification Type | Retry |
|---|---|---|---|
Technical Fault |
| None | Correct the connection issue. Resend the request from Customer Cloud Service. |
Business Fault |
| None | Correct the account or query parameters. Resend the request from Customer Cloud Service. |
Integration Process: OU CCS OPOWER Communication Content Get
Use the following table to diagnose content-link request failures, including an empty content path, before resending the request from Customer Cloud Service:
Type of Error | Action | Notification Type | Retry |
|---|---|---|---|
Technical Fault |
| None | Correct the connection issue. Resend the request from Customer Cloud Service. |
Business Fault |
| None | Correct the communication content path. Resend the request from OU CCS. |
Business Fault |
| None | Correct the query parameters. Resend the request from Customer Cloud Service. |
Integration Process: OU Common Configuration Properties Lookup Update
The following table describes failures when reading or updating configuration lookups. Check stored property values and destination results before retrying the calling flow:
Type of Error | Action | Notification Type | Retry |
|---|---|---|---|
Technical Fault |
| Handled by the calling flow. | Correct the lookup or connection issue. Verify the stored property values and destination results before rerunning the calling flow. |
Configuration Error | Capture and rethrow the error to the calling flow Process Stop | Handled by the calling flow. | Correct the lookup name or property name. Retry using the approved recovery procedure. |
Integration Process: OU CCS Common OS Transfer
The following table covers Customer Cloud Service Object Storage transfer failures. Verify whether an object was written before rerunning a failed upload:
Type of Error | Action | Notification Type | Retry |
|---|---|---|---|
Technical Fault |
| Handled by the calling flow. | Correct the Object Storage connection or permissions. Verify whether the object was written before rerunning the calling file-transfer process. |
Configuration Error |
| Handled by the calling flow. | Correct the destination configuration. Rerun the calling file-transfer process. |
Integration Process: OU CCS Common FTP Transfer
The following table covers Customer Cloud Service FTP transfer failures. Check destination settings and verify whether a file was written before rerunning the transfer:
Type of Error | Action | Notification Type | Retry |
|---|---|---|---|
Technical Fault |
| Handled by the calling flow. | Correct the FTP connection or permissions. Verify whether the file was written before rerunning the calling file-transfer process. |
Configuration Error |
| Handled by the calling flow. | Correct the destination directory or file reference. Rerun the calling file-transfer process. |
Resubmitting the Error Instances in Oracle Integration Cloud
In this integration, the flows initiated are asynchronous flows. The Resubmit option is available only for asynchronous flows.
To resubmit the error instances in Oracle Integration Cloud:
- Login to Oracle Integration Cloud.
- Navigate to Observability > Errors.
- Select the integration to resubmit.
- Click the Resubmit icon.
Email Notifications
This pre-built integration includes a configurable email notification when errors are encountered in Oracle Integration Cloud.
To receive a technical email notification:
-
Login to Oracle Integration Cloud.
-
Navigate to Projects > OU CCS OPOWER > Lookups.
-
Edit the OUTL-BRT-CCS_OPWR_TechnicalConfigProps lookup.
Change the
notif.email.technical.error.flagproperty value to “true”. -
Edit the OUTL-BRT-CCS_OPWR_TechnicalConfigProps lookup.
- In the from.email field, enter the email ID to receive an email from.
- In the technicalError.to.email field, enter the email ID to send the email to. Provide the comma separated email IDs.
-
Optionally, if want to receive technical information email, edit the OUTL-BRT-CCS_OPWR_BusinessConfigProps lookup.
Change the
notif.email.techerror.info.flagproperty value to “true”. -
Edit the OUTL-BRT-CCS_OPWR_BusinessConfigProps lookup.
- In the businessError.to.email field, enter the email ID to send the email to. Provide the comma separated email IDs.
To receive a business email notification:
-
Login to Oracle Integration Cloud.
-
Navigate to Projects > OU CCS OPOWER > Lookups.
-
Edit the OUTL-BRT-CCS_OPWR_BusinessConfigProps lookup.
Change the
notif.email.business.error.flagproperty value to “true”. -
Edit the OUTL-BRT-CCS_OPWR_TechnicalConfigProps lookup.
- In the from.email field, enter the email ID to receive an email from.
-
Edit the OUTL-BRT-CCS_OPWR_BusinessConfigProps lookup.
- In the businessError.to.email field, enter the email ID to send the email to. Provide the comma separated email IDs.