The config dumping occurs after the measurement is completed, so if the measurement is aborted (intentionally or unintentionally), the config does not get dumped even though partial output may have already been saved and so the measurement ID is not re-usable.
This primarily originates from allowing the final filename to only be fixed at the time of the actual measurement, and can be fixed by re-arranging this order of operations. We would have to be careful about how to "guarantee" the filename ahead of time and avoid race conditions.
The config dumping occurs after the measurement is completed, so if the measurement is aborted (intentionally or unintentionally), the config does not get dumped even though partial output may have already been saved and so the measurement ID is not re-usable.
This primarily originates from allowing the final filename to only be fixed at the time of the actual measurement, and can be fixed by re-arranging this order of operations. We would have to be careful about how to "guarantee" the filename ahead of time and avoid race conditions.