# Upgrading to 0.11.x or later using \`great\_expectations project upgrade\`: how are \`run\_id\` and \`run\_name\` populated?

**URL:** <https://discourse.greatexpectations.io/t/upgrading-to-0-11-x-or-later-using-great-expectations-project-upgrade-how-are-run-id-and-run-name-populated/312>\
**Category:** Archive\
**Created:** [August 12, 2020, 11:14pm UTC](https://discourse.greatexpectations.io/t/upgrading-to-0-11-x-or-later-using-great-expectations-project-upgrade-how-are-run-id-and-run-name-populated/312 "2020-08-12T23:14:44Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![wks](https://avatars.discourse-cdn.com/v4/letter/w/b77776/32.png) [@wks](https://discourse.greatexpectations.io/u/wks)\
**Post date:** [August 12, 2020, 11:14pm UTC](https://discourse.greatexpectations.io/t/upgrading-to-0-11-x-or-later-using-great-expectations-project-upgrade-how-are-run-id-and-run-name-populated/312/1 "2020-08-12T23:14:45Z")

</div>

What happens to the `run_id` and `run_name` for Validation Results when upgrading to GE 0.11.x or later using `great_expectations project upgrade` command? Are they upgraded automatically, or does it require manual intervention?

1. `run_name` is taken from old `run_id`. If run\_id can be parsed as datetime, it’s also used for `run_time`, otherwise `run_time` is generated from the creation date of file.  
2 . A consequence is that, in many cases, `run_name` and `run_time` will be the same
2. During this process the upgrader will log everything it does, so the specific changes can be access in the log files

More details on the upgrader logic can be found in the [source code](https://github.com/great-expectations/great_expectations/blob/develop/great_expectations/cli/upgrade_helpers/upgrade_helper_v11.py)
