That bug was a false positive. Turns out the correct WebClientExpection subclass is actually handled from the WebClient and later on information is wrapped with IllegalStateException which is then thrown from the callers of the downstream providers to the Cache Service.

In this I went to do a release tag v1.0.0 so that snapshot of the release is already captured and I can proceed to add observability later on for another release.

In the meantime, I need to go to the gym for some workouts.