I've seen this a handful of times and it's unclear why it is the case. It's not simple a matter of having not loaded yet - the Delete button, for instance, is inactive until the blade fully loads (and the little horizontal progress indicator at the top of the blade works as usual).
It is persistent across browsers/portal sessions, users, etc.
In the runbook editor(s), the Module appears to be loaded and expandable to see its members, but as this module was recently updated, I have no way of knowing if it is actually updated or if that's just the listing of the previous module. If something is so wonky with the 'provisioning' or 'importing' or 'extracting' that the portal can't even render the blade for the module, I have little faith that everything is A-OK under the covers.
Even worse, I have no way of interrogating any output from the operations in order to remediate any potential problems - as far as my code (or portal) is concerned, the module uploaded, imported, and extracted successfully, even though it didn't, actually.
I've noticed that some system-level jobs must be responsible for these imports/extractions, because the Job Statistics Monitoring Tile on the Automation Account ticks up the count when a module is being imported, yet these phantom Jobs don't actually show up in the Jobs list (and obviously, nor do the runbooks underpinning them).