← Connect blog

Engineering · Developers

How Connect picks a provider, and what it does when one fails

Ranked providers per operation, the failures that fall back, the one that never does, and why every attempt is in the response.

November 17, 2026 · 6 min read

One operation, several providers

When you call person.profile.find, you don't pick who answers. Connect holds an ordered list of providers for that operation and tries them in turn. Your code sees one request, one schema and one result.

The order is per operation, not per provider. A provider can be the best option for reading a page and a poor one for finding a person, and the list reflects that.

The failures that fall back

Not every failure should move on to the next provider. Connect separates them.

  • No match. The provider answered and found nothing. Try the next one.
  • Rate limited. Try the next one, and keep under each supplier's quota while doing it.
  • Provider outage. Try the next one, within limits on time and spend.
  • Authorization failure. Stop and report. Falling back would hide a real problem with a credential.
  • Uncertain completion. Reconcile. Do not retry.

Why writes are different

If a request times out, you can't tell whether the provider acted before the connection dropped. For a read, asking again is harmless. For a write, such as posting something or starting a paid job, it can run twice. So Connect records the outcome as uncertain and checks it, instead of sending the write again.

You see every attempt

The response lists each provider that was tried, what happened and what it cost. If a call took three seconds, you can see that the first provider timed out and the second one answered. Nothing is hidden behind a single success status.

What is next

Today the order is configured. We are working on choosing it from measured results, so you can ask for reliability, volume or speed and have Connect rank providers on that basis. That is not live yet, and the routing page says so.

One key. Start with a few dollars.

Try Connect on Konnect, or read the code and run it yourself.