A better approach is to display the created cases in a table sourced with proper case references and open them using OOTB case navigation, rather than only copying pyID and pzInsKey into a plain Page List and expecting the link to work automatically. case-opening behaviour depends on the correct open action and portal context, not just showing the case ID as a hyperlink.
Also, Instead of resolving the original case first and then creating additional cases from a local action, you could create the new cases before resolution by iterating over the date Page List. Pega supports creating multiple cases using a list, which is a more OOTB way to handle one-case-per-date creation.
Then, before resolving the original case , store the created case references on the initiator case and display them in a standard table/related-cases area. That way the newly created cases can be previewed and opened using OOTB case navigation rather than trying to manually construct links from pyID/pzInsKey after the fact.
Optionally, you can make tag the new cases as child cases and initiator case as a parent case which brings all the above options implicitly.
Another very practical alternative is to build a report/table of the cloned cases linked to the original trip case and let users open them from there, rather than relying on a manually constructed Page List link
Create a data page that can fetch these list of cases and configure a list view sourced from that data page in one of the tabs inside the interaction. Here you can configure the pyID column as a link to an object that can open cases. But, what I am not sure is whether these cases will be opened inside the interaction or outside of it.
If you copy these to a pagelist (embedded data in terms of constellation), system cannot form it as a link to a case. It treats it as a normal text.