'Nothing to save' message attempting to save environment after script-driven variable update

[michaelglasson]

I am updating my environment with a post-response script to record the most recent revision of the back end document. The updated value shows in the environment variables, but when I click on the Save button, I receive the 'nothing to save' message. I can write a script external to Bruno to update the environment, but that kind of defeats the purpose. Why is this important to me? Because a successful document update in the back end uses MVCC and that means including the latest document revision returned following a successful update. Without the ability to save the most recent version, my requests fail every time I restart Bruno. What about allowing the saving of the environment via the scripting api? Can we fix the issue where the environment configuration dialog does not know the environment has been updated by a script and so refuses to allow the 'Save' action to succeed?