Validation as a background task
Validation as a background task so UI isn't locked.
There are additional complexities with this such as what would happen if a network is being validated as a background task and someone then edits it, that validation couldn’t then be committed along with uncommitted changes. Regardless of how that aspect can be tackled, we are also looking into any options for optimising existing validation for speed.
If there are example models available showing slow validation users would be willing to share, please pass those on to support referencing this user voice suggestion so we can see what optimisation might be possible.
Nick Dahl commented
This is a huge problem with large networks and with large scenario numbers. Great suggestion.