We have made the decision to stop supporting regex.
The problem is that less than 1% of our users are currently using Regex and we continue to have problems with users entering regex strings that are complex enough to slow down processing for the rest of our user base.
We could investigate using a regex matching engine that would not allow this or we could write more complex code to execute the regex matches in their own process and kill it if it goes over a predefined amount of time but then we would have to somehow alert the user. So the complexity of implementing this quickly increases and with less than 1% of users even using regex, it does not make sense.
If you truly have a pattern matching use case that needs regex then let us know
We will get it implemented in our string matching algorithm or investigate other alternatives.
Later this year we will also be introducing a new string matching syntax that will be more performant, easier for users to build, and will more closely match the syntax users are used to in other platforms. This will co-exist with our existing syntax.
What we have been working on this past week
This past week we have been highly focused on migrating the frontend to leverage a modern JavaScript framework. This will allow a more seamless experience and for easier real-time eventing (notifications) in the frontend as well as a ton of other very cool features! We are doing this in phases so we can roll it out quickly and iteratively.