# Activate() not called when previous route uses same module?!

**URL:** <https://discourse.aurelia.io/t/activate-not-called-when-previous-route-uses-same-module/4648>\
**Category:** Help Requests\
**Created:** [February 21, 2022, 1:13am UTC](https://discourse.aurelia.io/t/activate-not-called-when-previous-route-uses-same-module/4648 "2022-02-21T01:13:30Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![ff-will](https://yyz1.discourse-cdn.com/flex027/user_avatar/discourse.aurelia.io/ff-will/32/1773_2.png) [@ff-will](https://discourse.aurelia.io/u/ff-will)\
**Post date:** [March 13, 2022, 8:36am UTC](https://discourse.aurelia.io/t/activate-not-called-when-previous-route-uses-same-module/4648/6 "2022-03-13T08:36:24Z")

</div>

While looking for a solution to dynamic routes in nested routers, I accidentally tripped of this post:

> [@The easy way to customize child router based on parent router param](https://discourse.aurelia.io/t/the-easy-way-to-customize-child-router-based-on-parent-router-param/768/15):
>
> Just to add some clarification to the above: activationStrategy.invokeLifecycle should be sufficient to ensure activate() is called. activate() is called by default when the route params have changed (which triggers the navigation plan to set the strategy to invokeLifecycle) activationStrategy.replace actually invokes the whole component lifecycle (including the templating’s bind(), attached() etc). The navigation plan normally only sets the strategy to replace when the moduleId has chan…

Apparently `activationStrategy.invokeLifecycle;` does the trick, no need to set it to `replace`.

---

_[View the full topic](https://discourse.aurelia.io/t/activate-not-called-when-previous-route-uses-same-module/4648)._