Thank you for your response.
From the release notes:
The variables action is no longer restricted to local scopes; it can now update the value of a variable also in outer scopes. If the variable was not previously defined, it will be created in the top-level (script run) scope
…
If you have automations or scripts that use the same variable name in different (previously isolated) scopes, you will need to update them: simply use distinct variable names to prevent any conflicts.
For example:
I trigger a script-chain in the living room while my wife is triggering another script in the kitchen. Both scripts triggers the same script to set a radio station, but the kitchen action will trigger this script before the action in the living room.
So, will the location variable ‘living room’ be overwritten with ‘kitchen’?