Workaround: Create Separate Unity Scheduler Task Groups and Services - Workaround: Create Separate Unity Scheduler Task Groups and Services - OnBase - Other - Content Conditioning - Other/Content-Conditioning/2.2/Content-Conditioning/Implementation-Instructions/Troubleshooting-Implementations/Error-Documents-Stuck-in-the-Processing-Queue/Workaround-Create-Separate-Unity-Scheduler-Task-Groups-and-Services - 2.2 - 2.2

Create a second Unity Scheduler service that runs Task Group specifically for the Content Conditioning timer/system work. This must be separate from the Task Group (or Unassigned group) that is running the HL7 Processor in the Unity Scheduler.

It may be considered a best practice to create separate Task Groups run by their own Unity Scheduler Service for Content Conditioning Tasks, HL7 Processor, and Chartless Processor.

Tech Support is looking into this further with R&D (Support Cases 00241736 and 00274599).