This is the first part of a bugfix for issue 250 [1]. The exception
was misleading because it was not really an inconsistecy but rather
lacking availability.

[1] #250

This is the first part of a bugfix for issue 250 [1]. The exception
was misleading because it was not really an inconsistecy but rather
lacking availability.

[1] #250

This is the first part of a bugfix for issue 250 [1]. The exception
was misleading because it was not really an inconsistecy but rather
lacking availability.

[1] #250

This is the first part of a bugfix for issue 250 [1]. The
exception was misleading because it was not really an
inconsistecy but rather lacking availability.

[1] #250

This is the first part of a bugfix for issue 250 [1]. The
exception was misleading because it was not really an
inconsistecy but rather lacking availability.

[1] #250

This InconsistentResultFromDifferentServersOfSameCurrency exception
type was introduced in [1], but after implementing an improvement[2]
over the exception message and type of another problem, I realised
that the new exception thrown in [2] wouldn't be covered by the
exception type mentioned above, so we need it to be more generic
(to receive any exception as innerException), so let's do that and
rename it.

This commit in conjunction with [2] don't really fix issue 250 [3],
but it might mitigate it, and anyway thanks to [1] if it happens
again, we will receive a different exception, with different
exception message as well, so let's close [3].

Closes #250

[1] 8fa47e0
[2] 5eca671
[3] #250

This InconsistentResultFromDifferentServersOfSameCurrency
exception type was introduced in [1], but after implementing an
improvement[2] over the exception message and type of another
problem, I realised that the new exception thrown in [2]
wouldn't be covered by the exception type mentioned above, so we
need it to be more generic (to receive any exception as
innerException), so let's do that and rename it.

This commit in conjunction with [2] don't really fix issue
250 [3], but it might mitigate it, and anyway thanks to [1] if
it happens again, we will receive a different exception, with
different exception message as well, so let's close [3].

Closes #250

[1] 8fa47e0
[2] 5eca671
[3] #250

This InconsistentResultFromDifferentServersOfSameCurrency
exception type was introduced in [1], but after implementing an
improvement[2] over the exception message and type of another
problem, I realised that the new exception thrown in [2]
wouldn't be covered by the exception type mentioned above, so we
need it to be more generic (to receive any exception as
innerException), so let's do that and rename it.

This commit in conjunction with [2] don't really fix issue
250 [3], but it might mitigate it, and anyway thanks to [1] if
it happens again, we will receive a different exception, with
different exception message as well, so let's close [3].

Closes #250

[1] 8fa47e0
[2] 5eca671
[3] #250

Backend: improve inconsistency edge case.

Closes #250