Blueprint synching canvas items out of order

[mlynch5]

Hi, everyone, 

I have had a few instances where my Blueprint courses are synching module items out of order in the associated courses.  I read some documentation on what to expect and saw this section found here: 

If modules or module items are rearranged in an associated course, the module order will be updated to match the blueprint course structure in the next sync. If a module item in an associated course is moved to another module, the module item will exist in both modules. 

The module items ended up being attached to the end of the module. The module in question was not manipulated by the enrolled teacher (we have multiple courses).

Any hypothesis of why this may have occurred? I would love to hear any thoughts or similar experiences.

Best,

M 

Some additional context that I'm not sure if it's relevant: 

• The module items that were placed out of order were copied over from another blueprint course and then placed in the Blueprint course that was used to synch. 
• The blueprint course is in a different sub-account than the associate course. 

[jerry_nguyen]

@mlynch5 

I also have the same issue occasionally. My workaround is to rearrange module items again (simply move it up and down few times to trigger the blueprint sync again).

Hopefully, Canvas will fix it in the future 🙂

[mlynch5]

Thank you, @jerry_nguyen ! I played around with moving around modules based on what you shared and realized that when I refresh the web browser the synchs are registered by the blueprint synch interface. I'm going to share with our team that a new practice might be refreshing the web browser before synching blueprints, especially if the last action was ordering module items. 

Appreciate you! 

[jerry_nguyen]

@mlynch5 

When you have a large number of associated courses, the ordering of module items might not be synced correctly. I normally have to trigger Blueprint sync multiple times to make sure the order is correct using the trick I mentioned.

Hopefully, Canvas is aware of this issue.