-1, I don't think we need to protect the user from knowing that his lambda was executed on a remote node. On the contrary, it might help him/her with debugging. FWIW, I don't think the cache should ever throw the exact exception that the lambda raised - I'd always wrap it in some kind of CacheException. Cheers Dan