JIRA Cloud bulk operation timeout due to webhook notifications

I had 250 issues to remove so did a bulk operation to delete. I selected 'dont send email' which stopped JIRA driven notifications. I had a registered external cloudservice consuming webhook notifications that has been otherwise able to consume all events. On this occasion, JIRA seemed to encounter a timeout of somekind, reporting a session expiry, all the issues were deleted in this case, and from what I can tell, webhook data was successfully sent, but, the point of this issue is that from the users perspective 'something went wrong', whatever caused this timeout or other, for a bulk delete needs to be more flexible, to take into account of delays talking to external systems.

This only happened with one addon and ~250 issues. I would imagine multiple addons and many more issues would result in the same, and (possibly?) also result in lost webhook notifications.

A suggestion would be to provide regular user on-screen feedback on numbers of issues 'dealt with' out of the total.