When running from within NCSA, services finish loading before the project/stacks/volumes as we expect. That way, when the stacks' services are loaded, the label of each service is looked up and displayed in the UI.

When running remotely, however, stacks sometimes finish loading before the service specs, preventing the UI from displaying them properly.

There are two ways that we could resolve this issue:

• Chain promises to represent the order that we want them to resolve
• Force the UI to update after services are loaded, so that we won't care about the resolution order

This ticket is complete when stack services resolve properly, regardless of whether the user is on-site or off-site, using one of the above strategies.