When a user terminates an active scenario by choosing "Select a network" from the dropdown menu, the frontend briefly displays "Select a network" but then forcefully reverts back to the previously selected simulated network. It stays stuck on the old network name until the backend finishes deleting all pods, which causes poor visual feedback and user confusion. **Root Cause:** This is caused by a Redux state race condition during the scenario teardown phase: 1. When termination is triggered, a local countdown timer (terminationInProgressCount) tracks the background deletion. 2. Because tearing down a heavy simulated network takes longer than the original 5-second timeout, the timeout expires while the backend is still deleting pods. 3. The frontend's active polling fetches the "stale" scenario data from the backend (which hasn't been cleared from Redis yet) and repopulates the global Redux state. 4. The configuration-pane.js component detects a mismatch between its local dropdown state ("Select a network") and the global Redux state (the stale scenario) and erroneously auto-syncs the dropdown back to the old network name.