Exceptions in the context of concurrent Eiffel programming (i.e. SCOOP) are implemented using a straightforward policy: the program is halted as soon as the exception occurs. Here I show why sometimes a programmer cannot really avoid this default behavior even with a rescue clause. A more flexible mechanism is therefore desirable. I introduce an exception model viable in the context of concurrent processors, and respectful of the exception model already in use in single-threaded programs.