Automated Relativity Incident and Exception Alerts
Every hour, WebRun checks Relativity for new processing failures, review holds, privilege exceptions, and other flagged incidents, logs each one to a Google Sheet, and fires an immediate Telegram alert to the litigation ops team when any exception count crosses your configured threshold.
How do I get automatic alerts when Relativity incidents or exceptions spike?
Every hour, WebRun checks Relativity for new processing failures, review holds, and privilege exceptions, logs each incident to a Google Sheets register, and fires a Telegram alert to the litigation ops team when any exception count crosses your threshold. The team can respond to incidents quickly without monitoring Relativity manually.
- The team is alerted within an hour when a Relativity incident crosses the threshold
- A complete exception register in Google Sheets shows incident history and trends
- All-clear confirmations mean silence is never ambiguous
Built for ediscovery processing teams · litigation support technicians · litigation ops managers · law firm IT
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
relativity.onein a real browser with your saved login - no setup, no API keys. -
1
Relativity - check for new incidents and exceptions
relativity.com
WebRun opens Relativity to check for new incidents and exceptions. - Open Relativity and check the event log and processing queue for new errors, holds, or privilege exceptions added in the last hour
- Capture incident type, matter name, document count affected, and the time the incident was logged
- Compare the new incident count against your configured hourly threshold for each incident type
Done when All new Relativity incidents in the last hour are captured and compared against thresholds.
-
2
Google Sheets - log incidents to the exception register
google.com
WebRun opens Google Sheets to log incidents to the exception register. - Open the incident exception register in Google Sheets
- Append each new incident as a row with timestamp, matter, incident type, document count, and threshold status
- Update the running daily total for each incident type
Done when All new incidents are logged in the exception register with their threshold status.
-
3
Telegram - alert the team when threshold is crossed
telegram.org
WebRun opens Telegram to alert the team when threshold is crossed. - If any threshold has been crossed, send an alert to the litigation ops Telegram group naming the matter, incident type, count, and time
- If all counts are below threshold, send a brief hourly confirmation that all systems are normal
- Include a link to the Google Sheets exception register in every message
Done when The team has received either an alert or an all-clear message via Telegram.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Does it resolve or acknowledge incidents in Relativity automatically?
No. WebRun only reads incident data and sends the alert. Incident resolution, hold releases, and exception remediation are handled manually by the processing or review team in Relativity.
What threshold should I set?
A good starting point is 10 processing errors or 5 privilege exceptions per hour. Set it lower for high-stakes matters. You can adjust the threshold per incident type in the settings.
Will the Telegram channel receive too many messages?
It sends one message per hour regardless - either an alert or a brief all-clear. It does not send multiple messages per threshold event, so the channel stays readable.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.