I realize it's a huge ask, but instead of JUST tearing down instances, maybe it can save a copy of the live environment in addition to the teardown so if we need to we can pop in and look at it, while also keeping the teardown functionality we use intact. Auto saved environments can be torn apart automatically in like....2 or 3 days or something. Just enough time for us to get into the lab and see what happened.
The reason I ask is because we deliver assessments to many customers, and every now and then we get extreme edge cases where the user environment breaks down in ways that are difficult-to-impossible to reproduce or diagnose.
If this could be done as a flag in the lab profile so we could apply this to our assessments or labs with issues it would make troubleshooting infinitely easier because relying on users to relay all the relevant information is a losing proposition.
Being able to hop into the final state of an environment would be the best troubleshooting feature of all time!
0
Unlikely to Implement
Following up with this idea, would the above suggestion of a recording work for this use case?
This would take a lot of internal discussion/evaluation before any definitive decision could be made. Would a recording of the user's session be a good alternative here? Being able to see exactly what they did within the environment as a post-session recording?
If so, this is something that is supported today and our teams can likely work with you to implement. Due to the many additional complexities that recordings result in it is hidden behind a number of criteria and permissions.