I faced the same issue (even with the same context generations). Unfortunately, the trick you described doesn't work for me.

As far as I can see in a stacktrace, a built-in framework's interceptor net.devh.boot.grpc.server.error.GrpcExceptionListener which processes @GrpcExceptionHandler annotations is called earlier than other GlobalServerInterceptors in a chain, that's why I'm not sure if @Order makes any effect here.

Could you guide me on how to reach a desirable behaviour?

Thanks!