Comment 1 for bug 2077189

This likely only occurs when the charm unit is RECONCILED yet has a blocked or waiting status.

If the charm wasn't reconciled -- an update-status event would force the charm back through the reconciler
However, because it's reconciled, only actionable juju events (relation-*, config-changed, etc.) would force us back through the reconciler.

Action events aren't reconciled -- and therefore they shouldn't really run inside a `status.context`