Posted: 14 Feb 2019 6:56 EST Last activity: 26 Feb 2019 11:18 EST
Activity method Queue vs Queue-For-Agent
We have a requirement to keep a track of all important user action in application. So on every important user action like search, update as case, advance a case we make an entry to a custom table. Our approach is to use Queue method in post processing activity and call the activity (say InsertLogs) that inserts a record in custom table.
It works fine until under normal circumstances but during high load we get few DB deadlock errors or the database takes longer time to run the merge DB script that is called from the InsertLogs activity.
Is there any better approach to handle this scenario? Can Queue-For-Agent perform better if we queue all the requests and process with a standard agent in every 2 hours or so.
***Edited by Moderator: Pallavi to update platform capability tags***