Skip to main content
Partner API create returns HTTP 409 with session_in_progress when another Suki product already has an active ambient session for the same emr_encounter_id. End that session, wait one second, then create again. On Headless Web SDK, the same kind of conflict is sessionAlreadyExists with blockingSessionId. Use sessionAlreadyExists remote session conflict for that path.

โ€‹
Common causes

  • Mobile SDK, Web SDK, or another API client left a session open for the same encounter.
  • Your app retries create without ending the open session first.
  • The conflict response has no blocking session id, so you must end the session from the product that still owns it.

โ€‹
Fix

1

Catch HTTP 409

On create failure, check for status 409 or a session_in_progress message in the body.
2

Read the Blocking Session Id

Read ambient_session_id from the conflict response when it is present.
3

End That Session

Call End ambient session with sdp_suki_token and sdp_provider_id. If the body has no id, end or cancel from the product that still owns the live session.
4

Wait One Second, Then Retry

Wait 1 second, then call create again with the same emr_encounter_id. See Resolve a remote session conflict.

โ€‹
Next steps

Resolve a remote session conflict - End the blocker, wait one second, retry create sessionAlreadyExists remote session conflict - Headless cancelRemote and endRemote Ambient and Dictation error messages - Look up session_in_progress Share one note across products - Shared emr_encounter_id across products End ambient session - Clear the blocking session over REST
Last modified on September 29, 2026