Shaina Cossairt I created a card in DevOps asking the team for guidance on how you, and potentially others, could best address this for post-migration tenants. I will keep you posted. DevOps #11607

Shaina Cossairt I did some digging in Cloud and QMS. Here is what happened. During a migration QMS will look at the PTD of the tenant, compare it to the delinquency template schedule for each task, and then skip those tasks that should have been completed in the prior software. That is what happened here, since the PTD was so far in the past, each skip date corresponds to the task date that QMS thinks the delinquency task occurred to ensure that it does not get posted again. So we know now the WHY, the bigger question is how do we address it now in QMS. There is no way to manually apply a specific delinquency stage in QMS. I believe the only workaround currently may be to exclude them delinquency, create a specific delinquency template for this unit to skirt the stage skipping, and then include them back into delinquency. Before you do anything though, let me see if Andre or the team have any other suggestions.

Shaina Cossairt Take a look at the eye icon for this tenant. It shows that those actions were skipped, so we probably need to take a look in Cloud to see what the data looks like and why those actions were skipped during the migration:

Tony Gardner New bug report