Post-upgrade rudiments
As you upgrade IA Cloud Enterprise, mistakes are possible, such as incorrect sequence of actions or a required step skipped. These entail post-upgrade rudiments: you have an updated IA Cloud Enterprise version, but some components or the entire platform are not operational.
Verify symptoms
You can identify post-upgrade OCR issues by the following symptoms:
As you run a Business Process (BP) with OCR, a request is sent from Control Tower to OCR, but you don't see anything processing.
In Marathon, you see OCR Workers running, the health check and OCR REST API work fine, but nothing is being processed.
Investigate
The best-practice recommendation is to look at the RabbitMQ queues with the previous OCR version in their names.
The most probable reason for the symptoms above is that, during the upgrade, the RabbitMQ queues might not have been deleted. So, when you launch OCR, BP tasks go to an older queue, whereas BEP components are looking for a new RabbitMQ queue.
Resolve
To resolve the issue, reconfigure the instance to work with a new RabbitMQ queue. For that, create a support request ticket via the Workfusion Support Service Desk. For instructions to submit a ticket, refer to the Raise tickets in WorkFusion Service Desk topic.
View also: