Hi all, we have been having a problem which has become more frequent recently, where the auto archiving process built in to Blue Prism, is competing for table lock with our regular SQL maintenance job. This is impacting several schedules as they are not starting while the BPASession/BPASessionLog tables are locked. The maintenance job runs out of hours at 23:00, and when it clashes with archiving, can lock the tables for up to 2 hours.
The session log table in particular is just shy of 40GB, and we keep 45 day's worth of logs for reporting purposes.
Are there any ways to prevent session log archiving from clashing with the maintenance task?
