Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Kishore Kumar (KishoreK8308)
Healthfirst Inc
Senior Consultant
Healthfirst Inc
US
KishoreK8308 Member since 2021 1 post
Healthfirst Inc
Posted: May 7, 2021
Last activity: May 10, 2021
Posted: 7 May 2021 7:40 EDT
Last activity: 10 May 2021 8:05 EDT
Closed

Queue Processor ready to process items

As part of claim processing , we are using one Queue processor to create a claim after receiving data in  as a json format.taking so much time to process the queue items.

***Edited by Moderator: Pooja Gadige to change category from Upgrade to Product, add platform capability tag***
To see attachments, please log in.
Pega Smart Claims Engine for Healthcare 8.5
Case Management
System Administration
Healthcare and Life Sciences
Experience Designer

Posted: 3 years ago
Posted: 10 May 2021 7:05 EDT
Kaviya Ravichandran (ravik2) Service Assurance Advisor
Pegasystems Inc.
IN

@KishoreK8308  Could you trace one queue item and check which part of code is taking longer time.

Or the processing slows because of the load on the node. In this case, recommendation is to distribute the load to other nodes as well.

To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice