It's not clear what problem we're solving here. Custom scripts and their outcome aren't generally something we'd consider our responsibility (it also sounds like this was a dry run, maybe?). If you're importing large amounts of data that might send lots of email, in retrospect it might also be good to disable emails during the import (we do this for repository imports, so code paths exists likely).

If the request is to provide alternative notification options other than emailing for each action, that already exists in your email preferences. If your server is busy enough that email is too noisy, our expectation is you could turn certain notifications off, leave others on-site only, and/or utilize your email client's filtering to keep things as you need.

@chad this was a one-time import script, not a dry run, and not run by me. I had very little warning, and certainly no warning about the volume involved.

I have disabled all emails for my account on the instance now, but batching events after a configurable amount of volume seems like it may not be a bad idea, even independent of this particular use case. Scripts are not the only thing that can cause the volume involved - I have personally made changes to over 200 tasks at once, and that certainly caused a lot of noise. I'm sure even more noise could be created with very little effort, from *within* the application.