Troubleshoot Common Error Scenarios

The table lists the common errors and exceptions which you may encounter while using the Oracle Intelligent Track and Trace application. For each scenario, a detailed description along with resolution steps are also provided.

Event Type	Error/Exception Scenario	Scenario Description	Resolution
Document Processing	Submitted document not complaint with schema	This error may be caused due to any of the following two reasons: Invalid Schema The JSON schema of the document type is incorrect. Incorrect Submitted document The submitted document is in invalid format and is not complaint with the document type JSON schema.	Invalid Schema Resolution: Check the JSON schema and make updates if necessary. Incorrect Submitted document Resolution: Re-submit the document with appropriate changes to ensure that the document is compliant with the schema.
Document Processing	Error storing transaction in document store.	This error is observed when the document with the specified key already exists. Duplicate ingestion of the same document is not supported. Example: Document with ledger key `'PurchaseOrder:44443941'` has been already stored.	Resubmit the document with a different ledger key. To understand more about ledger key, see Define Metadata Template
Document Processing	Unexpected error while processing event	Unexpected error happened with the system.	Contact your Oracle Support Representative.
Business Flow Processing	Error receiving document from object storage	The application is unable to fetch the document from OCI object storage, possibly due to network issue during connectivity.	Contact your Oracle Support Representative.
Business Flow Processing	Invalid hash of Object store document	Invalid document fetched from OCI document storage, possibly due to corrupted document.	Contact your Oracle Support Representative.
Business Flow Processing	Invalid JSON produced for metadata	Application of Handlebars template on the document produced invalid JSON. This could possibly be due to an issue with the metadata template.	Verify that the correct document template has been used to generate the JSON file. You can also run the simulation with the updated file to validate the document. Edit the metadata template to fix the syntax errors that caused the invalid JSON, and re-submit the document.
Business Flow Processing	Unexpected error while processing the document metadata. `java.net.SocketException: Network is unreachable`	This error is observed when there is a connectivity Issue with the infrastructure.	Contact your Oracle Support representative.
Blockchain Processing	Error invoking BCS transaction proxy `Unauthorized OBCS admin example@example.com`	Incorrect BCS configuration.	Correct the BCS configuration and then re-submit the document.
This is not an exception event	Documents show up in separate flow instances	This is a potential error which may be caused due to incorrect document cross-reference mapping in the metadata template.	Verify the metadata template against the submitted document to check if the mapping matches. You cannot replay this as the document with incorrect cross-reference is already processed successfully. Currently, there is no way to fix this as the document is already recorded in the blockchain.
This is not an exception event	Flow instance view shows incorrect flow relationships	This is a potential error which may be caused due to incorrect cross references between the documents.	Verify the submitted documents in the flow instances against the cross-references provided in the corresponding document type metadata schema. You cannot replay this as the document with incorrect cross-reference is already processed successfully. Currently, there is no way to fix this as the document is already recorded in the blockchain.