Invoke-PnPSiteTemplate giving error while provisioning ClientSidePage in nested folder

<pnp:Provisioning xmlns:pnp="http://schemas.dev.office.com/PnP/2021/03/ProvisioningSchema">
<pnp:Preferences Generator="PnP.Framework, Version=1.5.0.0, Culture=neutral, PublicKeyToken=null" />
<pnp:Templates ID="CONTAINER-TEMPLATE-3388C301FA2944FBBBFDFF32EB0F425C">
<pnp:ProvisioningTemplate ID="TEMPLATE-3388C301FA2944FBBBFDFF32EB0F425C" Version="1" BaseSiteTemplate="SITEPAGEPUBLISHING#0" Scope="RootSite">
pnp:ClientSidePages
<pnp:ClientSidePage PromoteAsNewsArticle="false" PromoteAsTemplate="false" Overwrite="true" Title="Executing Task" ContentTypeID="0x0101009D1CB255DA76424F860D91F20E6C411800F7AB37DA6658EF4FB78CC37790338E4C" ThumbnailUrl="" PageName="getting/Test/task1.aspx">
<pnp:Header Type="Custom" ServerRelativeImageUrl="" LayoutType="NoImage" ShowTopicHeader="false" ShowPublishDate="false" TopicHeader="" AlternativeText="" Authors="[]" AuthorByLine="[]" AuthorByLineId="-1" />
</pnp:ClientSidePage>
</pnp:ClientSidePages>
</pnp:ProvisioningTemplate>
</pnp:Templates>
</pnp:Provisioning>

When PageName is provide inside root or first level folder, provisioning gets successful. But not inside nested folder as give n in above template

Start with the Invoke-PnPSiteTemplate entry point and reproduce the XML using ClientSidePage PageName="getting/Test/task1.aspx". Compare provisioning for root, first-level, and nested folders; done means the nested-folder page provisions successfully without regressing the working cases.