50109: Conversation role not found

This error occurs when the roleSid in your request does not match a Role resource in the target Conversation Service. Roles are scoped to a Conversation Service, and Twilio uses service-level roles for Users and conversation-level roles for Participants.

• The roleSid value does not reference an existing RL... Role SID. Twilio expects a valid Role resource when you assign a role to a User or Participant.
• The role exists in a different Conversation Service. If your application uses more than one service, you must specify the correct IS... Service SID instead of relying on the default shortened endpoint.
• The request uses the wrong role scope. Users require a service-level role, while Participants require a conversation-level role.

• Fetch the role or list roles for the target Conversation Service and confirm that the roleSid you send is present before you retry the request.
• If you work with multiple Conversation Services, send the request against the correct service-scoped endpoint and use the matching IS... Service SID for the role, user, or participant you are updating.
• Assign the correct role type for the resource you are updating. Use a service role for a User and a conversation role for a Participant.
• If the role does not exist yet, create it first with the correct type and permissions, then retry the request with the new RL... SID.

• Role Resource
• Conversations (classic) User Resource
• Service-Scoped Conversation Participant Resource