You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Today if a user calls DurableOrchestrationClient.StartNewAsync or DurableOrchestrationContext.CallFunctionAsync and specifies a function name which doesn't exist, the call fails silently.
Instead, these methods should throw an exception that can be handled/logged by user code.
The text was updated successfully, but these errors were encountered:
This is fixed in the latest release. If you try to call a function that doesn't exist, an exception will be thrown and the message will include all the active function names, making it easier to figure out what went wrong.
Today if a user calls
DurableOrchestrationClient.StartNewAsync
orDurableOrchestrationContext.CallFunctionAsync
and specifies a function name which doesn't exist, the call fails silently.Instead, these methods should throw an exception that can be handled/logged by user code.
The text was updated successfully, but these errors were encountered: