"ODM Teams - Maximum number of tabs allowed on the thread is set to '50'" Error During Archive Channel Post Migration (4380929)

The customer reported that approximately xx.xxx Teams messages were not archived during the migration. The ODM logs showed the following error:

Request failed with BadRequest status code (Bad Request).
{"error":{"code":"BadRequest","message":"Maximum number of tabs allowed on the thread is set to '50'. The channel already has '50' tabs" ... }}

This occurred when ODM attempted to create additional tabs in the Teams channel to display archived chat history.

This issue is caused by a Microsoft Teams API limitation. Each Teams channel has a hard limit of 50 tabs, as defined by Microsoft.

During the archive process, the ODM tool generates HTML files containing archived Teams messages and attempts to attach them as individual tabs within the target Teams channel.

When the number of existing tabs (including default tabs) plus newly added archive tabs exceed the limit, Microsoft blocks the creation of additional tabs, triggering a 'BadRequest' error.

This is not a limitation of Quest ODM, but rather an enforced restriction within Microsoft Teams.

1. Delete the entire affected Team or specific channels from the target tenant and perform a full team re-migration from the source tenant. This helps avoid the tab limit caused by excessive archived content or unnecessary automated messages.
2. Alternatively, delete unused tabs and their corresponding archive .html files within the affected channel to free up tab slots. After clearing space, re-run the archive migration option to generate new archive tabs as needed.
3. Re-attempt the archive using the "Archive All Messages" option after freeing up space to ensure all messages are archived properly.

Note 1: Archived messages from a successful previous attempt will not be recreated unless the original archive failed or the messages were modified.

Note 2: In all scenarios new task must be created.