Given that notifications are in the wild and arbitrary notification types can now be added, it makes no sense to maintain a fixed schema with a limited number of valid types any longer.

The existing enum is already breaking validation for legitimate events generated by Flow. I modified Schema:Echo and removed the enum so we can recover these missing events [1]

However, this approach is not going to be viable in the long term. As with campaigns, we will need to replace the current dashboards and data processing scripts (which assume a fixed schema) with something more flexible.

[1] https://meta.wikimedia.org/w/index.php?title=Schema%3AEcho&diff=7572295&oldid=6081131

Version: unspecified
Severity: normal