Advanced agent running on multiple nodes causing case save failure
we have a requirement to Resolve work objects using agents. because of huge load during business hours, we have enabled the agent in two nodes.
The agent does Obj-browse on 500 records at a time and resolves each record. Even configured at different times, The agent in different nodes is starting to run exactly at same time (even secs) and pulls the same records and trying to save the workobject at same time. this save is getting failed to database.
how can we avoid this?
**Edited by Moderator Marissa to update categories & update SR Details***
In a production application, work item data volume can grow to a size where hundreds of megabytes of database storage are required. The Purge/Archive wizards enable you to use an agent to automatically delete old work item data from the respective tables and/or store them in ZIP archive files. Purging and archiving old work items and their related history and attachment records help maintain system performance by reducing database processing demands.