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.
Summary of Integration Error Handling
There are different errors and can be handled in a different way. These are the common types of errors, and all emails are being send via the OU Common Notification Handler integration.
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 fault is sent back to the respective system as part of immediate response.
Errors in Integration Processes
Integration Process: OU WACS OIC GISMappings Sync
Type of Error
Action
Notification Type
Retry
The attribute size is more than 2k characters.
• Process stops.
• OIC instance is marked as ‘failed’.
Business Error Email (Code 400)
Make sure the size of attributes are less than 2k characters. Or, remove the attributes that are more than 2k characters from the WACS mappings lookup data.
 
Reschedule the execution in OIC.
Remote fault:
• WACS is down.
• Lookup is not available in OIC.
• Process stops.
• OIC instance is marked as ‘failed’.
Remote Error Email
• Verify that the lookup OUTL-BRT-ArcGIS_WACS_AssetClass is present in OIC.
• Verify that the WACS is down or not.
• Reschedule execution in OIC.
 
Integration Process: OU ArcGIS WACS Assets Sync
Type of Error
Action
Notification Type
Retry
Incorrect parameters
• Process stops.
• OIC instance is marked as ‘failed’.
Business Error Email
Reschedule the execution in OIC.
Remote fault
• Process stops.
• OIC instance is marked as ‘failed’.
Technical Error Email
• Activate the OU ArcGIS WACS Initial Assets Sync or OU ArcGIS WACS Incremental Assets Sync integrations.
• Reschedule the execution in OIC.
Unexpected Error
• Process stops.
• OIC instance is marked as ‘failed’.
Technical Error Email
• Review the error email and correct the issue.
• Reschedule the execution in OIC.
 
Integration Process: OU ArcGIS WACS Initial Assets Sync
Type of Error
Action
Notification Type
Retry
Incorrect Attributes, URL
• Process stops.
• OIC instance is marked as ‘failed’.
Technical Error Email (Code 400)
Attributes in the OIC lookup should not be modified manually.
 
For invalid URL, verify the connection details and RelativeURI in OUTL-BRT_ArcGIS_WACS_AssetClass.
 
Reschedule the execution in OIC.
Remote fault
• Process stops.
• OIC instance is marked as ‘failed’.
Technical Error Email
• Verify the OIC connection to the ESRI ArcGIS server.
• Activatee the OU WACS Common OS Transfer or OU WACS Common FTP.
• Reschedule the execution in OIC.
Unexpected Error
• Process stops.
• OIC instance is marked as ‘failed’.
Technical Error Email
• Review the error email and correct the issue.
• Reschedule the execution in OIC.
ArcGIS Error retry
• If “arcgis.retry.error” is true, keep invoking ArcGIS service up until “arcgis.retry.count”. If error persists, default to error.
Business Error and Technical Error Email
• Review the error email and correct the issue.
• Reschedule the execution in OIC.
 
Integration Process: OU WACS ArcGIS Assets Update
Type of Error
Action
Notification Type
Retry
Technical errors occurring at the beginning, such as:
• Invalid values for schedule parameter
• Errors loading datetime values from the lookup
• Process stops.
• OIC instance is marked as “failed”.
Technical Error Email
• Fix Errors
• Reschedule execution in OIC
Functional errors occurring during the processing of each file, such as:
• Invalid lookup values
• Invalid Tokens
• Errors while writing or reading from stage files
• ArcGIS returning errors during update operations
• Errors will be collected.
• Process will continue to next iteration.
• The affected file will be renamed with a prefix “ERROR_”.
Business Error Email
• Fix Errors
• Rename files with prefix ERROR_.
• Reschedule the execution in OIC.
ArcGIS error retry
If “arcgis.retry.error” is true, keep invoking ArcGIS service up until “arcgis.retry.count”. If the error persists, default to error.
Business Error and Technical Error Email
• Review the error email and correct the issue.
• Reschedule the execution in OIC.
 
Integration Process: OU ArcGIS WACS Incremental Assets Sync
Type of Error
Action
Notification Type
Retry
Incorrect Attributes, URL
• Process stops.
• OIC instance is marked as ‘failed’.
Technical Error Email (Code 400)
Attributes in the OIC lookup should not be modified manually.
 
For invalid URL, verify the connection details and RelativeURI in OUTL-BRT_ArcGIS_WACS_AssetClass.
 
Reschedule the execution in OIC.
Remote fault
• Process stops.
• OIC instance is marked as ‘failed’.
Technical Error Email
• Verify the OIC connection to the ESRI ArcGIS server.
• Activate the OU WACS Common OS Process or OU WACS Common FTP Process.
• Reschedule the execution in OIC.
Unexpected Error
• Process stops.
• OIC instance is marked as ‘failed’.
Technical Error Email
• Review the error email and correct the issue.
• Reschedule the execution in OIC.
ArcGIS error retry
If ‘arcgis.retry.error’ is true, keep invoking ArcGIS service up until ‘arcgis.retry.count’. If the error persists, default to error.
Business Error and Technical Error Email
• Review the error email and correct the issue.
• Reschedule the execution in OIC.
 
Integration Process: OU WACS ArcGIS Assets Update
Type of Error
Action
Notification Type
Retry
Technical errors occurring at the beginning, such as:
• Invalid values for the schedule parameter.
• Errors loading datetime values from lookup.
• Process stops.
• OIC instance is marked as “failed”.
Technical Error Email
• Fix errors.
• Reschedule execution in OIC.
Functional errors occurring during the processing of each file, such as:
• Invalid lookup values
• Invalid Token
• Errors while writing or reading from stage files
• ArcGIS returning errors during update operations
• Errors will be collected.
• Process will continue to next iteration.
• The affected file will be renamed with a prefix “ERROR_”.
Business Error Email
• Fix errors.
• Rename files with prefix ERROR_.
• Reschedule the execution in OIC.
ArcGIS error retry
• If “arcgis.retry.error” is true, keep invoking ArcGIS service up until “arcgis.retry.count”. If error persists, default to error.
Business Error and Technical Error Email
• Review the error email and correct the issue.
• Reschedule the execution in OIC.
 
Integration Process: OU ArcGIS WACS Incremental Assets Sync
Type of Error
Action
Notification Type
Retry
Incorrect Attributes, URL
• Process stops.
• OIC instance is marked as ‘failed’.
Technical Error Email (Code 400)
• Attributes in the OIC lookup should not be modified manually.
• For invalid URL, verify the connection details and RelativeURI in OUTLBRT_ArcGIS_WACS_AssetClass.
• Reschedule the execution in OIC.
Remote fault
• Process stops.
• OIC instance is marked as ‘failed’.
Technical Error Email
• Verify the OIC connection to the ESRI ArcGIS server.
• Activatee the OU WACS Common OS Process or OU WACS Common FTP Process.
• Reschedule the execution in OIC.
Unexpected Error
• Process stops.
• Review the error email and correct the issue.
Technical Error Email
• Review the error email and correct the issue.
• Reschedule the execution in OIC.
ArcGIS error retry
• If “arcgis.retry.error” is ‘true’, keep invoking ArcGIS service up until “arcgis.retry.count”. If the error persists, default to error.
Business Error and Technical Error Email
• Review the error email and correct the issue.
• Reschedule the execution in OIC.
 
Integration Process: OU WACS ArcGIS Work Location Sync
Type of Error
Action
Notification Type
Retry
Technical errors such as ArcGIS Service unavailability or others.
Process stops.
• OIC instance is marked as “failed”.
Technical Error Email
• Fix errors.
• Resend message either from OIC or WACS.
Functional errors: When ArcGIS encounters an issue, it returns a description in the payload. This is sent back to WACS, where it is logged as part of the outbound sync request.
ArcGIS error description is sent back to WACS.
• Process is marked as successfully completed..
Error logged in Outbound Message in WACS
• Fix errors
• Resend message from WACS.
ArcGIS error retry: ArcGIS API requests can be automatically retried for specific errors, as defined in the arcgis.retry.error.codes property in OUTL-BRT-ArcGIS_WACS_ConfigProps
If “arcgis.retry.error “ is true, keep invoking ArcGIS service up until “arcgis.retry.coun t”. If error persists, default to error.
If the service continues to fail due to a technical error, a Technical Error Email is sent.
• Fix errors.
• Resend message either from OIC or WACS.
 
Integration Process: OU WACS Common OS Process
Type of Error
Action
Notification Type
Retry
All faults
• Process stops.
• OIC instance returns the fault and is marked as ‘failed’.
N/A
Retry the OU ArcGIS WACS Initial Assets Sync or OU ArcGIS WACS Incremental Assets Sync integration.
 
Integration Process: OU WACS Common FTP Process
Type of Error
Action
Notification Type
Retry
All faults
• Process stops.
• OIC instance returns the fault and is marked as ‘failed’.
N/A
Retry the OU ArcGIS WACS Initial Assets Sync or OU ArcGIS WACS Incremental Assets Sync integration.
 
Integration Process: OU Common Notification Handler
Type of Error
Action
Notification Type
Retry
All faults
• Process stops.
• OIC instance returns the fault and is marked as ‘failed’.
N/A
N/A