When I look at active tasks under “Dashboard” → “Monitor”, I notice that QPOC and QPOC - HIGH are running more than 50% of the time. This makes it difficult to put in identity profile updates as any running QPOC task does not allow you to update identity profiles.
What is the cause of QPOC and QPOC - HIGH running so consistently? Have others experienced this same issue?
Hi @dominick-miller could you please tell us if you reviewed VA logs.
@dominick-miller while some of the processes and status around QPOC/QPOC - HIGH are internal and not publicly documented, there are few things that you might want to look into:
QPOC seems to run when there are aggregations and identity refreshes. You may see something in the Dashboard/monitor page that looks like
For me I was updating an Identity Profile on approximately 300 users. If you watch this page, you should see the number decrease as they are processed.
The other thing that might be forcing QPOC are scheduled aggregations. If you have many sources aggregating frequently, your system might always be in a state of continual reprocessing. You can see this from the Dashboard/Aggregation Activity or using the API call /beta/task-status. You will be able to see what ran what whether it successfully completed. You might be able to pause these aggregations while you complete your Identity Profile. If you don’t have many aggregations but they are long running, you might check to see (1) does your VA have enough resources and (2) is there any way to optimize your aggregation? (For example, if this is a SQL aggregation that is slow, can you improve the query or work with the database administrator on tuning the database response?)
You may also have tasks that are “stuck” due to some error. For example, in my environment, I had an error in a workflow that left several tasks pending. You can see this using the api /beta/task-status/pending-tasks
It will return a payload like
If this is something that you can accomplish otherwise, you can take the ID from the pending-tasks and patch the task to completion using /beta/task-status/:id. The body should look something like
Reducing tasks that would otherwise never complete might help your overall system performance.
Hope this helps,
Alicia
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
