Error Handling
This section provides information about the different ways used to handle errors in the integration and also resubmitting the instances after rectifying the errors.
Error Handling Ways
In this integration, the errors are handled in different ways due to the limitation of Oracle Integration Cloud.
Synchronous Flow Error Handling
As part this error handler the errors are sent back to the respective system in the same flow.
Technical Fault
This fault occurs when there is a data mismatch or any Xpath related error. On this error, the flow immediately goes to global fault handler and the fault is sent back to the respective system.
Remote Fault
This fault occurs when the target system is down. When this error occurs the flow immediately goes to global fault handler and the fault is sent back to the respective system.
Business Fault
This fault occurs only when the business fault occurs in the target system due to invalid data. When this error occurs the error information is sent back to the respective system as a fault.
Asynchronous Flow Error Handling
Technical Fault
This fault occurs when there is a data mismatch or any Xpath related error. When this error occurs, the flow immediately goes to global fault handler and an optional email to the respective user is sent.
Remote Fault
This fault occurs when the target system is down. When this error occurs, the flow immediately goes to global fault handler and an optional email is sent to the respective user.
Business Fault
This fault occurs only when the business fault occurs in the target system due to invalid data. When this fault occurs, the error information is sent to the source system and an optional email notification is sent to the respective user.
Summary of Integration Error Handling
Integration Process: Oracle Utilities WACS OFSC Admin Data Sync
Type of Error
Action
Notification Type
Retry
Remote Fault
 
Example: WAM IWS or OFS API is not accessible
Process Stop
Email
Resubmit the flow from OIC.
 
Integration Process: Oracle Utilities WACS OFSC Activity Process
Type of Error
Action
Notification Type
Retry
Business Fault
Example: Invalid activity type
Continue
Email
Make sure the activity type exists in WACS and OFS, and then resend the request from WACS.
Remote Fault
Example: Child integration flow is not active
Process Stop
Email
Ensure "Activity Pull Update" integration flow is active and then resend the request from WACS.
Remote fault
Ex: OFS API invocation error
Process Stop
Email
Resend the request from WACS.
Attachment file size exceeded
Process Stop
No notification is sent.
Error message is replied to WACS.
Resend the request from WACS after fixing the attachment size issue.
Attachment count exceeded
Process Stop
No notification is sent.
Error message is replied to WACS.
Resend the request from WACS after addressing the attachments count issue.
 
Integration Process: Oracle Utilities OFSC WACS Activity Complete
Type of Error
Action
Notification Type
Retry
Remote Fault
 
Example: WAM IWS or OFS API is not accessible
Process Stop
Email
Resubmit the flow from OIC.
 
Integration Process: Oracle Utilities OFSC WACS Resource Usage Details
Type of Error
Action
Notification Type
Retry
Remote Fault
Example: WACS IWS invocation error
Process stop
Email
Once the service is up, resend the request from the respective OFS screen.
 
Integration Process: Oracle Utilities OFSC WACS Activity Interim Status
Type of Error
Action
Notification Type
Retry
Remote Fault
Example: WACS IWS invocation error
Process stop
Email
Resubmit the error instance from OIC once WACS IWS is accessible.
 
Integration Process: Oracle Utilities OFSC WACS Asset Query
Type of Error
Action
Notification Type
Retry
Business Fault
Example: Missing data, such as:
• Location/Organization is missing.
• Invalid location for asset installation.
• Asset does not exist.
Process Stop
Email
Perform asset query again with valid values, from OFS.
Remote Fault
Example: WACS IWS invocation error
Process Stop
Email
Perform asset query once WACS IWS is accessible or up.
 
Integration Process: Oracle Utilities OFSC WACS Work Order
Type of Error
Action
Notification Type
Retry
Remote Fault
Example: WACS IWS or OFS REST API invocation error
Process stop
Email
Resubmit the error instance from OIC.
 
Integration Process: Oracle Utilities OFSC WACS Work Request
Type of Error
Action
Notification Type
Retry
Remote Fault
Example: WACS IWS or OFS REST API invocation error
Process stop
Email
Resubmit the error instance from OIC.
 
Integration Process: Oracle Utilities WACS OFSC Storeroom Admin Sync
Type of Error
Action
Notification Type
Retry
Remote Fault
Example: WACS IWS or OFS REST API invocation error
Process stop
Email
Resubmit the error instance from OIC.
Or, run the scheduler flow manually.
 
Integration Process: Oracle Utilities OFSC WACS Storeroom Sync
Type of Error
Action
Notification Type
Retry
Business Fault
Example: If the truck sent from OFS does not exist in WACS
Process stop
Email
Ensure both WACS and OFS data is in sync. Then, run the Schedule Storeroom Sync OIC flow.
Remote Fault
Example: WACS IWS invocation error
Process stop
Email
Once WACS service is accessible, run the Schedule Storeroom Sync OIC flow.
 
Integration Process: Oracle Utilities WACS OFSC Schedule Storeroom Sync
Type of Error
Action
Notification Type
Retry
Remote Fault
Example: If child OIC flow is not accessible
Process stop
Email
Resubmit the error instance from OIC.
Or, run the scheduler flow manually.
 
Integration Process: Oracle Utilities OFSC WACS Route Activation
Type of Error
Action
Notification Type
Retry
Remote Fault
Example: If store room sync child OIC flow is not accessible
Process stop
Email
User has to retry the activation from OFS.
 
Integration Process: Oracle Utilities OFSC WACS Activity Pull Update
Type of Error
Action
Notification Type
Retry
Remote Fault
Example: WACS IWS invocation error or OFS API invocation error
Process stop
Email
If it is a WACS initiated update, resend the activity update request from WAM through the Process Activity flow.
 
If it is an OFS initiated update request, perform Refresh Activity from OFS.
 
Note: Please note the following:
• Make sure all Oracle Integration Cloud lookups are configured with valid data.
• In case of the Oracle Field Service initiated flows that are event based, if Oracle Field Service to Oracle Integration Cloud communications fails, Oracle Field Service will retry the error events until the Oracle Integration Cloud communication is successful.
• The time limit is 36 hours. After that, all event subscriptions will be deleted in Oracle Field Service.
Resubmitting the Error Instances in Oracle Integration Cloud
In this integration, the flows initiated by Oracle Field Service are asynchronous flows, and the resubmit option is available only for asynchronous flows.
To resubmit the error instances in Oracle Field Service:
1. Login to Oracle Field Service.
2. Navigate Monitoring > Integrations > Errors.
3. Select the integration to resubmit.
4. Click the Resubmit icon.