Adjust report snapshot & retention retrieval timeout

Updated 10/12/2022

In certain distributed network topologies, you may find that camera snapshots are not coming through in the camera report.  This may be due to increased latency across the network.  In this case, you can adjust the snapshot timeout for both the Boring Toolbox reports as well as the reports run through the web app and scheduled reports. 

Boring Toolbox ad-hoc reports

• Close Boring Toolbox if open
• Navigate to: "C:\ProgramData\The Boring Lab\Boring Toolbox\{username}\Config\"
• Edit the file settings.json
• In the document find the following settings (Please see the screenshot below):
  • "RequestTimeoutInSeconds" 
  • "ReportSnapshotTimeout". 
• Set the value of each to 30
• Save & Close the file
• Open Boring Toolbox and generate an ad-hoc report with retention from the "Camera Report" section. See the screenshot below.

Scheduled reports and reports performed via the web app

• Navigate to "C:\Program Files\The Boring Lab\Milestone Proxy\"
• Open your text editor as Administrator
• In the text editor open appsettings.json
• In the document find HardwareCheckTimeout (see the screenshot below)
• Set the value to "00:00:30"
• Save & Close the file
• Open Boring Web and try to generate another report with camera retention and snapshots included.