Knowing how long a simulation solve takes can be vital to troubleshooting. If it's reasonable, having a time estimate on how long a solve may take would save a lot of time. Users could simply cancel the solve if the estimate is far too long and examine the model for reasons why it would take that long. The reason I suggest this is because the model I'm working with is difficult to run solves on; often times, if I choose to, I could leave the cloud solve running for several hours with the status bar in the same location throughout. I now know it was because the model is difficult to mesh, but it was not obvious from my first time running. There could also be more information under the down arrow (something more specific than "solving"), so users could tell what is causing a lengthy solve time.
