The following table describes how to address known connection issues that may affect Intelligent MedRecords (IMR).
| Service Task/Integration Error | Note | Resolution |
|---|---|---|
|
Content with correlation id <uniqueID> finished with status FAILED and message Error Retrieving Content, An unexpected error occurred at the broker |
This means the error occurred downstream. Open diagnostics console on the machine with MCA installed and replay the task. |
Fix the associated keyword or access issues This may be an issue outside of CIC. |
|
Content with correlation id <uniqueID> finished with status FAILED and message Content not found, Request Content could not be found |
This may be a service interruption. Replay the service task. | |
|
Content with correlation id <uniqueID> finished with status FAILED and Invalid Scope |
There may be an issue with allowed scopes on the external application. Scopes should be:
The allowed application should be Content Federation Content Consumer API. |
Validate that the uniqueID in the error message matches the application ID for the external application.
|
|
ServiceUnavailable: {"title":"Service Unavailable","status":503,"detail":"An unexpected error occurred. Contact your administrator or support team for assistance","eventId":1100,"activityId":"<activityId>"}
|
This may be a service interruption. Replay the service task. |
|
|
Failed to get content |
Try replaying the service task. This may simply be a service interruption. |
|
|
DD_ENV is missing in configuration |
This means configuration is missing on the backend. |
|
|
Error: MethodNotAllowed |
Ensure the lookups are set up correctly in the class group configuration. |