Archiving Error- Session is already composed for given tag with code 409

Symptom

An error is thrown with the message "Session is already composed for given tag with code 409" when using multiArchiveTag feature

Applies To

• Archiving

Resolution

The error could occur because you may not be setting the unique multiArchiveTag for the second or subsequent archive that you are starting on the same session. The multiArchiveTag is the tag of the archive, with which to start, this is unique for each archive within the session.

Additional Information

Here’s an example of the POST data of an archive with MultiArchiveTag

{
    "sessionId" : "session_id",
    "hasAudio" : true,
    "hasVideo" : true,
    "layout" : {
      "type": "custom",
      "stylesheet": "the layout stylesheet (only used with type == custom)",
      "screenshareType": "the layout type to use when there is a screen-sharing stream (optional)"
    }
    "name" : "archive_name"
    "multiArchiveTag": “MyArchiveTag”, //

A unique multiArchiveTag will trigger a new archive on the session.  

(Note: If no tag is provided only one archive will be allowed, to preserve backward compatibility)