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
If the underlying NL network call fails (due to 429, 500, 400 or whatever - the reason doesn't matter here ) -
what should Power Apps do? At the very least, they probably want to get that error and log it. But they may also want to do something in the UI (tell user it failed).
How should that error be communicated at NLHandler?
Return a specific object? Ie, with an error field filled out.
Throw an exception? If so, which exception.
We're seeing FxHttpResponseException thrown from the IntelligenceApiAuthenticatedChannelBase.SendAsync .
But this is an internal exception defined in internal repo; and not publicly part of the contract. It becomes unhandled and bubbles up through LSP as an unhandled exception.
The text was updated successfully, but these errors were encountered:
If the underlying NL network call fails (due to 429, 500, 400 or whatever - the reason doesn't matter here ) -
At API level, we need to sort out NLHandler and comment it clearly:
https://github.com/microsoft/Power-Fx/blob/main/src/libraries/Microsoft.PowerFx.LanguageServerProtocol/Public/NLHandler.cs
Should it:
We're seeing FxHttpResponseException thrown from the IntelligenceApiAuthenticatedChannelBase.SendAsync .
But this is an internal exception defined in internal repo; and not publicly part of the contract. It becomes unhandled and bubbles up through LSP as an unhandled exception.
The text was updated successfully, but these errors were encountered: