---
"@context": https://schema.org
"@type": TechArticle
"@id": https://www.twilio.com/docs/api/errors/80614#article
headline: "80614:  No Partner Participant Found"
url: https://www.twilio.com/docs/api/errors/80614
inLanguage: en
dateModified: 2026-06-08T12:04:59.000Z
author:
  "@type": Organization
  name: Twilio Developer Education Team
publisher:
  "@type": Organization
  name: Twilio
---

# 80614:  No Partner Participant Found

Log Level: WARNING

## Description

This warning means Proxy received an inbound message or call from a participant in a session, but could not find the other participant to route that interaction to. Proxy is built for one-to-one masked communications, and a session supports up to two participants.

### Possible causes

* The session has only one active participant, so there is no partner participant available to receive the inbound interaction.
* The partner participant was removed from the session. A removed participant has a `dateDeleted` value, and that participant is no longer available for routing.
* Your application created the session before both participant records were present, or replaced a participant before the inbound call or message arrived. Proxy routes each participant through the partner participant's `proxyIdentifier`, so routing fails when that counterpart is missing.

### Possible solutions

* Fetch the session and list its participants to confirm the session is still active and that two participants are present for the conversation. Check the session `status`, `ttl`, and `dateExpiry` if inbound traffic is arriving later than expected.
* If the session is missing the second participant, add a new participant with a valid `identifier`. If you specify `proxyIdentifier`, make sure that number is in the Proxy number pool for the service.
* If you removed the original partner participant, create a new session for that user flow instead of trying to add the same identifier back to the existing session. After a participant is removed, you cannot add that same identifier back to the same session.
* If your workflow needs to handle messages or calls that arrive after a session closes or no longer exists, configure `outOfSessionCallbackUrl`. You can use that callback to return TwiML or auto-create a new session.

#### Additional resources

* [Participant resource](/docs/proxy/api/participant)
* [Session resource](/docs/proxy/api/session)
* [Out-of-Session Callback Response Guide](/docs/proxy/out-session-callback-response-guide)