# Resume tuning after updating search space with more hyperparameters

**URL:** <https://discuss.ray.io/t/resume-tuning-after-updating-search-space-with-more-hyperparameters/9354>\
**Category:** Uncategorized\
**Created:** [February 13, 2023, 2:41pm UTC](https://discuss.ray.io/t/resume-tuning-after-updating-search-space-with-more-hyperparameters/9354 "2023-02-13T14:41:15Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![wxie2013](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ray.io/wxie2013/32/3419_2.png) [@wxie2013](https://discuss.ray.io/u/wxie2013)\
**Post date:** [February 14, 2023, 8:04pm UTC](https://discuss.ray.io/t/resume-tuning-after-updating-search-space-with-more-hyperparameters/9354/9 "2023-02-14T20:04:01Z")

</div>

That’s actually what I did for a different issue in the following thread:

> [@Correct way of using tuner.restore()](https://discuss.ray.io/t/correct-way-of-using-tuner-restore/8247/4):
>
> According to the source code comments, the restore() function is only for “”"“Restores Tuner after a previously failed run.”. If a previous run is not failed, then the restore() function will just printout the tuned result from the previous run.

---

_[View the full topic](https://discuss.ray.io/t/resume-tuning-after-updating-search-space-with-more-hyperparameters/9354)._
