Symptoms
Client event notifications were not being received.
Diagnoses
A quick check of the EventBus.ClientRecorderError table turned up this gem:
System.Exception: Unable to resolve a value for the following field '' using provider '' with provider data ''. 'SourceCode.Framework.Data.GetValueException: An unexpected error has occured while trying to resolve a value for Resolver ID 106C5886-18B1-4c09-BEB3-6F7342669D18. ---> SourceCode.Framework.Data.GetValueException: An unexpected error has occured while trying to resolve a value for Resolver ID 22d1b47c-1d4a-4a8f-9f7e-3cb991e144c6. ---> SourceCode.Framework.Data.GetValueException: An unexpected error has occured while trying to resolve a value for Resolver ID 71a54e2e-9109-41da-851d-ea8b86404e0c. ---> SourceCode.Framework.Data.GetValueException: An unexpected error has occured while trying to resolve a value for Resolver ID 22d1b47c-1d4a-4a8f-9f7e-3cb991e144c6. ---> System.Exception: The function 'ToDecimal' raised a 'TargetInvocationException' during execution. ---> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.FormatException: Input string was not in a correct format.
at System.Number.StringToNumber(String str, NumberStyles options, NumberBufferand number, NumberFormatInfo info, Boolean parseDecimal)
at System.Number.ParseDecimal(String value, NumberStyles options, NumberFormatInfo numfmt)
at System.Convert.ToDecimal(String value, IFormatProvider provider)
at System.Convert.ToDecimal(Object value)
--- End of inner exception stack trace ---
at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
at System.Reflection.MethodBase.Invoke(Object obj, Object[] parameters)
at Source
This implicates a ToDecimal function being problematic for the client event notifications.
Resolution
A check of the workflow showed that there was in fact a ToDecimal function getting used removing that allowed client notifications to resume as intended.
