What means "Replayed revision 176 of 3351"? Why would it take so long?

[ser789654]

Hi, when I start migration it keeps repeating this countdown:

[07:49:09 INF] [16.0.9] EmbededImagesRepairEnricher: Fixing HTML field attachments for work item 90 from https://dev.azure.com/MobileApp/ to https://dev.azure.com/*****/
[07:49:09 INF] [16.0.9] TfsWorkItemEmbededLinkTool: Fixing embedded mention links on target work item 90 from https://dev.azure.com/MobileApp/ to https://dev.azure.com/****/
[07:49:10 INF] [16.0.9] [                Task][Complete:     1/7251][sid:   359|Rev:3351][tid:  null |  Saved TargetWorkItem 90. Replayed revision 176 of 3351

What does it mean?

Also can you give me estimation of how long can migration of 7251 woriktems take? Yesterday I run it on my PC for 4 hours and I got to only 200/7251. Can I speed it up somehow? Maybe I should spin up VM in cloud and let it run couple days?

[MrHinsh]

These tools are designed for people who know Azure DevOps and how it works. Do you perhaps know someone who can help you?

---

Every save to a Work Item is a revision. The work item that you describe has been saved 3351 times, and to move it across, we need to do 3351 saves on the new location. This is usually an indication of some kind of 3rd party automation that has been setup on your system that edits work items. Typically, I would expect a work item to have between 10-25 revisions, and with outliers as much as 200.

3351 revisions is way beyond normal and as it takes about 400ms per save in the TFS Object Model that we use your work item with 3351 revisions will take around 25m.

If you got 200 work items saved in 4h, that's around 36,000 revisions or an average of 180/ work item, which is super abnormal. You might want to chat with the Azure DevOps Organisation Owner and see whats been happening with the system.

In addition we use a stateless system and load all of the work item revisions into memory and I would expect if you have many work items in this state that it could also take a considerable amount of time to load before the migration starts.

We do have some features to mitigate this!

• MaxRevisions - In the TfsRevisionManager you can set MaxRevisions to limit the number of revisions that are migrated for each work item. If you set it to say 20, we will save the oldest revision (when the item was created) and then skip to the top 20.
• ReplayRevisions - If you set this to false we will only bring across the latest revision.

---

We generally work on this tool through 1) customer funding, or 2) donated free time. If you have an urgent need, you can Hire us directly to provide managed migration servers, migration advice, or new features for this tool.