If a system is currently recovering from a MUPdate, noticing that the planner is blocked is not entirely clear without looking directly at the blueprint logs. Ideally there would be some way of indicating the fact that the planner is currently blocked, as well as the reasons if so, stored on the blueprint itself -- either in a comment or perhaps in a more structured manner, so that blueprint displays are clearer.

@plotnick this might intersect with the work you've been doing with tracking planner waiting steps.