Finch unable to provide a connection

Can you confirm that the upstream service is healthy and capable of handling your load?

Keep in mind that Finch connections are lazy—they only initiate new connections when needed. If the upstream service is degraded at that time, try to open a new connection may result in a timeout.

may I please clarify by the upstream service you mean the external API to which Req makes requests? If so, yes time to time they can respond with 429 but not that often. from 1200 requests per minute only 600 were handled, for all others I got the mentioned above error.
Is there a way to make connections eager?

Yes! I was referring to the external API that Req makes requests to.

Given the occasional 429 responses, it seems likely the issue is related to the service being unable to establish a new connection when Finch requires a new one (due to lazy initialization).

To confirm, you could try lowering the pool size and pool count (perhaps even setting it to 1) and see if the error persists. If this is indeed the issue, you’ll likely see timeouts, but the connection pool should remain functional and not raise this error.

Thank you very much Gabriel
Is the following setup correct in general? And also pull size 1, does it slow down the performance?

Seems correct! But it for sure slow down the performance and the way it is right now it would apply for all services called by this MyConfiguredFinch instance.

So, I would suggest 2 things:

• Create a configuration for the specific service you are having trouble with.
• Do not decrease it to 1 on the first try, but measure and see

Somehting like this:

children = [
      {Finch,
             name: MyConfiguredFinch,
             pools: %{
               :default => # Keep as it is
               "https://your-faulty-service.com" => [size: 10, count: 1]
             }},

It helped but not totally, less but still getting the same error, is there buy chance a way to catch this particular error? I can see only RuntimeError without any additional markers

You could probaly match on it’s message on a catch/2

My suggestion now would be increasing :pool_timeout option on Finch request. See Finch — Finch v0.23.0

Since some of your requests take a long time (eg. 15 seconds) you may end up starving the pool.

One way to measure it is to start pool metrics on finch with the option :start_pool_metrics? on Finch start_link. See Finch — Finch v0.23.0

And then run a periodically job that will execute Finch.pool_status/2 and gather this metrics so you can check if your pool is starving or not.