Automated Relativity Processing Exception Monitoring
Every morning, WebRun opens Relativity, reads the processing error and exception report for each active matter, logs every exception to a shared Google Sheet, and sends a Telegram alert when the total exception count exceeds your threshold so the processing team can fix issues before review starts.
How do I automatically flag Relativity processing exceptions before review starts?
WebRun checks the Relativity processing module each morning for errors and exceptions, logs every new exception to a Google Sheet with date, matter, and error type, and sends a Telegram alert to the processing team when the exception count exceeds your threshold. Issues are visible before they stall a review.
- Processing exceptions are spotted and logged every morning before review begins
- The team receives an instant Telegram alert when exception counts spike
- A complete exception history in Google Sheets shows trends over the life of each matter
Built for ediscovery processing teams · litigation support technicians · law firm IT · legal operations
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 - read processing errors and exceptions
WebRun opens Relativity to read processing errors and exceptions. - Open Relativity and navigate to the Processing module for each active matter
- Read the current exception report, capturing error type, document count, and processing set name
- Record any new exceptions not already in the tracker
Done when All current processing exceptions are captured with their type, count, and matter name.
-
2
Google Sheets - log exceptions to the tracker
WebRun opens Google Sheets to log exceptions to the tracker. - Open the processing exception tracker sheet for the matter
- Append each new exception as a row with date, matter, processing set, error type, and document count
- Update the running total column so the team can see exception trends over time
Done when The Google Sheet has an up-to-date log of all exceptions, including today's additions.
-
3
Telegram - alert when exception count exceeds threshold
WebRun opens Telegram to alert when exception count exceeds threshold. - Check whether today's total exception count exceeds the configured threshold
- If it does, send an alert to the processing team Telegram group listing matter, exception types, and total count
- If below threshold, send a brief daily confirmation that processing looks clean
Done when The processing team has received either an alert or a clean confirmation 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 fix processing errors automatically?
No. WebRun reads and logs exceptions and sends an alert when counts spike. Resolving errors in the Relativity processing module is done manually by the processing team.
What threshold triggers the Telegram alert?
The default threshold is 50 exceptions per processing set, but you can set any number in the run settings. You can also set different thresholds for different error types.
Will it alert even on days with no new exceptions?
Yes. It sends a brief daily confirmation to the Telegram group either way, so silence is never ambiguous - you will always know it ran.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.