With the 2.0.x series of Branch API, saving the configuration only triggers a re-scan if the configuration has been changed in such a way that a re-scan is required.
Previously, saving the configuration would always result in a re-scan and hence you could not effectively rename (unless you opened a second window and sat watching for the computation to complete)
With the 2.0.x series you can now rename as illustrated in the attached GIF
- The first attempt to rename fails, because the computation is in progress - this is by design
- Then we confirm that the computation has completed and now the rename succeeds