We have had some reports that some customers are being adversely impacted by the missing retry behavior in grpc-js. In particular, apparently some auth errors encountered in the wild are transient, so when those failures do occur, a client with retries enabled will retry the call and eventually successfully authenticate, but a client without retries will immediately report an error to the user.
Any progress on this one? Or maybe a guide how to handle errors in this client implementation? At which errors we should retry and at which we should create a new client?
@murgatroid99