Over the weekend we released the following updates to Heropa. We look forward to your feedback!  

✨ Features

• Pin VMs: We've made it easier to access VMs you work with regularly via a new Pin VM feature. See: Working with VMs in the workspace.
• AWS status check: A tool has been created to help troubleshoot failed connections to AWS VMs. See: AWS VM status check.
• Notify users by email when a new environment is created: Select to notify a user via email when a new environment is created for them. See: Creating and launching an environment.
• Copy content sections: At a section level, content can now be copied and inserted into into other content, making it easier to re-use content. See: Creating content.

🌱 Enhancements

• Events - Classroom thumbnails: Thumbnails are now retrieved directly from the server without requiring local user workspace information. This should result in a significant improvement in the delivery of thumbnails in the Classroom view.
• User session management: Some general enhancements to user session management were implemented to better recycle stale user sessions.
• Deleting a VM within an Environment: When deleting a VM, the name of the VM is now shown to the user prior to deletion.
• Dashboard role permission optimisations: It's now possible to restrict a role's visibility of the Dashboard. See: Using Roles and Permissions.

🔧 Bugfixes 

• Terraform updates are now asynchronous: Updates to existing environments incorrectly showed a failed / rollback status. This was due to the synchronous implementation of Terraform updates to AWS. We have now implemented asynchronous updates, removing the false positive failure status.
• Updating Environments: Row actions available for specific environment states were incorrect and could lead to unwanted actions being available for selection. These have now been updated so only applicable actions based on the environment state can be selected.
• User timeline: For some users, timeline information was not visible in the User Details / Timeline tab due to required data fields being missing. This has now been resolved. 
• Reconnecting to disconnected VMs in the workspace: This was only updating once a successful connection was established, and not showing the attempted reconnection in progress. This has now been resolved.