We understand, Pega is maintaining routing table rule internally -which help to display the Portal, when we open a case via Sematic URL .

We have observed, whenever, we are updating a view in a landing page,  pyRoutingTable rule is getting created in that branch.

We used to merge the entire branch in a RSV and move that to target env and thus the pyRoutingTable rule gets deployed to the target env . 

Sometimes , we are observing , though the latest routing rule is present in that target env --still in application rule we got an error saying -"Please unlock ruleset to update routing table "( attached image) .When , we get this error -sometimes , we are observing the portals are not generated properly and sometimes there is no as such issue altogether.   As part of the resolution -->We unlock the rsv and generate the routing table again in the traget env and then lock the ruleset back .

I need some guidance- Though , we move the routing table rule explicitly as part of code deployment, then why that error is coming? Are we missing anything or it is recommended to explicitly generate routing table after each code deployment  ?