That is unlikely to suffice going forward. You and your fellow developers will continue abusing tag events until this pops back up. The correct answer is to offload anything that calls out to a database or across a network. Use a gateway event script, or a custom thread pool executor, or, in special cases, an independent thread. (Ignition's store and forward system is ideal for offloading database inserts and updates.)
Regardless, you should be instrumenting your tag events with java's System.nanoTime() and logging detailed warnings for anything that takes 10ms or more.
Thanks for the info Phil. It is not the intent to abuse the tag event. However, this is a project we were asked to work on that was inherited from another company. It utilized large UDTs with extensive use of tag event scripts. A complete re-development of the existing system would have been necessary to correct this (not an option). It was our (bad) luck to be the ones to hit this limit. This is something I will remember in the future...