Known Connection Issues - Known Connection Issues - The following table describes how to address known connection issues that may affect Intelligent MedRecords ( IMR ). - Content Innovation Cloud - OnBase - Other - Intelligent MedRecords - Other/Intelligent-MedRecords/1.0/Intelligent-MedRecords/Administration/Troubleshooting/Known-Connection-Issues - 1.0 - 1.0

Intelligent MedRecords

Platform
Other
Product
Intelligent MedRecords
Release
1.0
License
ft:lastPublication
2026-02-26T23:39:32.053000
ft:locale
en-US

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:

  • environment_authorization
  • cfs-content-consumer-api
  • cf-consumer-api

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.

  • If they do not match, then edit the connector parameters.
  • If they do match:
    • Validate the allowed scopes and allowed application on the external application.
    • If scopes are correct, edit connector parameters.
    • If issue persists, undeploy and redeploy the 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.

  1. Edit connectors parameters.
  2. Undeploy and redeploy the application.

Error: MethodNotAllowed

 

Ensure the lookups are set up correctly in the class group configuration.