livekit/livekit · error
not implemented
Error message
not implemented
What it means
Stub error: RoomManager.ForwardParticipant always returns it — the participant-forwarding RPC is declared in the interface but not yet implemented on this server, so any ForwardParticipantRequest is unconditionally rejected.
Source
Thrown at pkg/service/roommanager.go:903
Attributes: req.Attributes,
}, true); err != nil {
return nil, err
}
if req.Permission != nil {
participant.GetLogger().Debugw(
"updating participant permission",
"permission", req.Permission,
)
participant.SetPermission(req.Permission)
}
return participant.ToProto(), nil
}
func (r *RoomManager) ForwardParticipant(ctx context.Context, req *livekit.ForwardParticipantRequest) (*livekit.ForwardParticipantResponse, error) {
return nil, errors.New("not implemented")
}
func (r *RoomManager) MoveParticipant(ctx context.Context, req *livekit.MoveParticipantRequest) (*livekit.MoveParticipantResponse, error) {
return nil, errors.New("not implemented")
}
func (r *RoomManager) PerformRpc(ctx context.Context, req *livekit.PerformRpcRequest) (*livekit.PerformRpcResponse, error) {
room := r.GetRoom(ctx, livekit.RoomName(req.GetRoom()))
if room == nil {
return nil, ErrRoomNotFound
}
participant := room.GetParticipant(livekit.ParticipantIdentity(req.GetDestinationIdentity()))
if participant == nil {
return nil, ErrParticipantNotFound
}
resultChan := make(chan string, 1)View on GitHub (pinned to ee45c3f0b1)
Solutions
- Do not send ForwardParticipantRequest to a server that returns this error
- Check for a server version that implements participant forwarding
- Use an alternative mechanism (e.g. participant migration APIs) if available
Defensive patterns
Strategy: fallback
When it happens
Trigger: Thrown at pkg/service/roommanager.go:903 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of livekit/livekit@ee45c3f0b1 (2026-09-02).
Data as JSON: /api/errors/f5f3c0115c8ab72b.
Report an issue: GitHub.