-
-
Notifications
You must be signed in to change notification settings - Fork 153
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Realtime alerts should group whenever possible #3102
Comments
This is done for RECAP in #4200 I'll use this issue to apply grouping also for Oral arguments RT alerts. |
To be clear, I think this applies across all RT alerts, no? |
Yeah, that's correct. For now, we need to apply it to Oral Argument RT alerts, which is the other document type supported by the Percolator. |
Yep, let's get on it. :) |
What are we holding this open for? |
Yes, this is still open since the review of #4251 is pending. |
I signed up for real time alerts for all oral arguments, and today I got three emails at almost exactly the same time because we scraped three items from the DC circuit all at once. Instead of doing that, we should send one alert with all three.
This will become more important as we move to RECAP, because we'll be getting dozens or even hundreds of docket entries at a time, and we should be sure we only send one email when that happens.
One solution is to delay RT alerts by a few minutes, but that's pretty unsatisfying (this is how Stackoverflow does it, but still). If we can, we should try to be smarter about how we send. Some of our users insist that ever second counts.
The text was updated successfully, but these errors were encountered: