Error Handling
This section provides information about the different ways errors are handled in the integration.
Summary of Integration Error Handling
Integration Process: CSS DACS Customer Sync Transfer (applies to OIC flows FTP and OS)
Type of Error
Action
Notification Type
Retry
Technical Fault
 
Example: Source FTP or Source Object Storage is not accessible or missing permissions to read source folder or write in the target folder
Process Stop
Error Email
Next scheduled run will pick up the files from CCS source content server or manually run the OIC process.
Technical Fault - Partial Processing
 
Example: One of the files sizes is bigger than 1 GB or a network connection issue.
• Files processed before the 1 GB file error is encountered are transferred to the target location.
• When the error is encountered, process stops.
Error Email
 
Process Complete Email
 
(include the list of files transferred and not transferred)
Next scheduled run will pick up the files not transferred from CCS source content server or manually run the OIC process.
Business Fault
 
N/A since the integration only transfer files
N/A
 
N/A
 
Integration Process: Customer Sync Ack
Type of error
Action
Notification Type
Retry
Technical Fault
 
Example: CCS is not accessible.
Process Stop
Error Email
Resend message from DACS
Business Fault
N/A
N/A
N/A
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:
1. Login to Oracle Integration Cloud.
2. Navigate to Integrations > Monitoring > Errors.
3. Select the integration to resubmit.
4. Click the Resubmit icon.