Inconsistent Call Structure
The one call goes to the agent and the second call in an internal repository. The architecture must be modified in this way, that the service uses just the internal data structures. Otherwise it behaves in one case like a proxy, and in the other case with custom behavior. Example:
find proof presentation uses internal repo, connection id available. find proof presentation by id uses the agent in the background and does some magic to transform the response. This is quite intransparent during the debugging and leads to inconsistencies.
Edited by Cristina Pauna