We have recently run into two tickets where the errors returned by WT (e.g. EINVAL and WT_ERROR) didn't come with sufficient context for us to decide what to do, uncovering a need for more granular errors from WT. Instances can also occur where the error gets propagated to users in a misleading manner.

This ticket is to investigate the possible solution of querying a WT session for more context once an error code has been returned. This can be done in parallel with the other stream of investigation (see linked WT ticket) to identify which one sticks better.