There’s something in RavenDB which every platform developer should copy into their own platforms: Well written exception messages. Here’s one example:

The maximum number of requests (30) allowed for this session has been reached.
Raven limits the number of remote calls that a session is allowed to make as an early warning system. Sessions are expected to be short lived, and
Raven provides facilities like Load(string[] keys) to load multiple documents at once and batch saves.
You can increase the limit by setting DocumentConvention.MaxNumberOfRequestsPerSession or DocumentSession.MaxNumberOfRequestsPerSession, but it is
advisable that you'll look into reducing the number of remote calls first, since that will speed up your application signficantly and result in a
more responsive application.

Not only does this tell you what went wrong, it also tells you why and also offers advices on how to fix it. Does it get any better than this?

Good exceptions can be real time-savers.