Do not reset error occurrences for non-production releases
Since today, when a release is triggered for any non-production environment, the occurrences of errors are not reset anymore. Only when a release is triggered for a production environment are errors reset and notifications about re-occurring errors sent again.
This is a temporary change in behavior until Tideways can store, reset and notify about error occurrences for each environment individually.
See the documentation Deployment Events for more information.
About the author
I am the founder and CEO of Tideways. I started the company over 10 years ago with the mission to move the PHP ecosystem forward, starting with performance. As managing director, I work across product, strategy, and the day-to-day of building a developer-focused SaaS business.
I’m a core contributor to the Doctrine open-source project and a founding board member of the PHP Foundation, which reflects my long-standing commitment to the PHP ecosystem. I particularly enjoy working at the intersection of application performance, developer experience, and the open-source community that makes PHP what it is. Outside of work, I enjoy board games, hiking, and coffee.