If a service is called from a 'when invoke' and it has caching enabled, this can lead to misunderstanding when it returns cached values instead of the expected mocks that it might be calling.
Cached services called within a service do not experience this problem and are correctly mocked, it only affects a service invoked from the story.
It may be possible to trigger the resetting of the cache value by intercepting the service invoke from the session that's invoking the test. Debugging has shown the service is intercepted. Careful consideration required how to implement so as not to introduce overhead for all non-intercepts.
If a service is called from a 'when invoke' and it has caching enabled, this can lead to misunderstanding when it returns cached values instead of the expected mocks that it might be calling.
Cached services called within a service do not experience this problem and are correctly mocked, it only affects a service invoked from the story.
It may be possible to trigger the resetting of the cache value by intercepting the service invoke from the session that's invoking the test. Debugging has shown the service is intercepted. Careful consideration required how to implement so as not to introduce overhead for all non-intercepts.