title: Mitigating Cloud Run's limitation regarding Cloud SQL connections per instance
body: <p>I link my Cloud SQL instances to Cloud Run with the <code>--add-cloudsql-instances</code> argument.</p>
  <p>Some requests are getting 500 Internal Server error in it's responses. Looking at the logs, I was able to know that Cloud Run <strong>&quot;Exceeded maximum of 100 connections per instance...&quot;</strong>. I know that Cloud Run limits to 100 the number of connections that each Cloud Run instance can do to Cloud SQL.</p>
  <p>I have already tried to set lower concurrency levels in my Cloud Run service as a way to avoid each instance from exceeding the limit, but the problem never dies. What can I do to mitigate this behaviour and bring my application back to normal stability?</p>
  <p>PS. I can't find good and recent answers on this anywhere in the internet, so I decided to ask here.</p>
  <p>Details about my last Cloud Run revision: 4 vCPUs, 6GB of RAM, --concurrency of 32.</p>