A few weeks ago, a @telebugs user shared a really insightful request that hit home for anyone running critical applications.
They manage systems where every error (even rare ones) needs immediate attention. Marking an error as “resolved” is helpful for organization, but it shouldn’t prevent alerts if the issue happens again.
Their words summed it up perfectly:
“We have apps doing critical stuff. If someone forgets to un-resolve an error, we miss the next occurrence. We need a way to get notified on every instance, resolved or not.”
It was exactly the kind of feedback that makes building Telebugs so rewarding. This isn’t a one-size-fits-all tool. Real teams have nuanced workflows, and this use case (low-volume, high-signal projects) deserved a dedicated solution.
Good news: I’ve implemented it.
Coming in the next release: “Notify on every occurrence”
This new rule will alert you on every single instance of an error, regardless of the resolved state.
Ideal for:
- Mission-critical apps
- Compliance-driven environments
- Teams that treat every exception as urgent
- Projects where “resolved” is more of a temporary note
- It’s deliberately powerful (and noisy), so it’ll be opt-in and best used selectively on projects where volume is low.
This will land in the next version update - stay tuned for the release notes.
A huge thank you to the user who raised this (and to everyone who shares ideas). Listening to you is how #telebugs keeps getting better for real-world use.
Excited to ship this soon. If you have feedback or other workflow needs, reply or DM (I read it all).
Kyrylo Silin