This message was deleted.
# helpdesks
steep-balloon-41261
12/21/2023, 9:41 PMThis message was deleted.
r
rich-machine-35023
12/21/2023, 10:39 PMLikewise, I’d like to better what the
EgressStatusrich-machine-35023
12/21/2023, 11:22 PMAlso, when doing API error handling, at least from the js sdk, the error type is
AxiosErrord
dry-elephant-14928
12/22/2023, 11:13 PMthat's great feedback. the enums values can be found here, but I agree it's pretty confusing.
you should be able to reference the type from the JS SDK tho.
Regarding API error handling, it's not guaranteed that it'll be
AxiosErrorr
rich-machine-35023
12/23/2023, 12:55 AMYeah so I did look through all the proto files but it’s kinda unclear what event would cause the corresponding error status
rich-machine-35023
12/23/2023, 12:56 AMFor the api error handling, it’d be useful if as part of that change, the sdk wrapped the underlying axios or fetch exception into a livekit specific one
👍 1
rich-machine-35023
12/23/2023, 12:59 AMAnd kinda on that same note, it’d be nice to have in the documentation what errors calls would return in the course of normal operation, so that we know in which cases the calls should be retired. For example, when I was testing yesterday, I found that calling stop on an already stopped egress raised a twirp error of 503, which usually is a transient and retriable error code, but is not in this case, which is why some additional documentation would be useful.
rich-machine-35023
12/23/2023, 1:00 AMAlthough this is all obviously just kinda regarding error handling. In the course of normal operation the apis and documentation are quite straightforward and easy to use 🙂