One of our users tried to place a hold on a few files. The hold worked for several of the files, but 5 files received the following error. We have no idea what is different about these files, or why the hold failed.
@BRiach do you have the CONNECT and THREAD logs as they will indicate why the adding of the hold failed at the application level. If you have a developer they can also trace through the code to see which rules caused these files to return that response as well.
We do not appear to have logs for the days this happened, but we can retry the holds to recreate. What level of logging needs to be set for THREAD or CONNECT to capture these errors? @vholguin
I would set the logging as high as you can to ensure you capture the details.