Receiving "Connection lost: The server closed the connection." with createPool

When calling execute or query from a Pool returned from createPool, I'm occasionally getting the error "Connection lost: The server closed the connection.". This error looks like it is coming from a stream close event in connection.js.

My understanding is that Pool should automatically capture this condition and recreate a connection, but that does not appear to be happening (i.e. I don't understand why I would be seeing this error when using Pool.execute or Pool.query. I'm not seeing anything in Pool.getConnection/query/execute that appear to be set up to handle a closed connection. Do I need to write my own error handling around this?

As context, I'm using this from Lambda to connect to RDSProxy, so that makes it even more fun to diagnose :)

Thanks

Start in connection.js at the stream close event, then trace Pool.getConnection, Pool.query, and Pool.execute to see how closed connections are handled. Reproduce the failure if possible in the Lambda/RDSProxy context and define done as Pool operations recovering from a closed connection without exposing the connection-lost error.