Inexplicable errors on container statistics page when state changes

Supposed when a container with the `running` state switches over to `exited` state, there are no issues.


But when a container with the `exited` state is monitored and during that, it switches over to a `running` state - errors show up.


The driver code works totally fine but there's something that needs to be done to ask the users to reload the page as the container state has changed.

Start at the container statistics page and reproduce the transition from exited to running while it is being monitored. Trace the page's handling of the changed container state and verify that the user receives guidance to reload the page instead of the reported errors. Done means this transition no longer shows inexplicable errors and clearly asks the user to reload.

Written by the indexing model from the issue text.