With 2022 Release Wave 1 Microsoft introduced "Isolated Events":

An isolated event ensures the event publisher continues its code execution after calling an event. If an event subscriber's code causes an error, its transaction and associated table changes will be rolled back. The execution continues to the next event subscriber, or it will be handed back to the event's caller.

This feature is perfect for making the overall system stability at critical points not dependent on a single subscriber.

The OnCompanyClose() event is just such a place. But currently its not a isolated one.

The disadvantage that results from this is relatively simple: if only one app causes an error in this event, the client and thus the session cannot be closed cleanly.

But this also leads to the fact that background sessions can not be closed successfully. which in turn leads to the fact that for example no app can be installed if only one other app causes an error in the OnCompanyClose() event.

Isolated events were invented for exactly this use case, so we should also use them.