@PatrickDLR : I think with other responses you are aligned with advantages for reuse but to address your query and for clarity on this post about your thoughts from User conference conversations:AEM Guides as a product is used for multiple other advantages but not only reuse - and considering that u...

@Asutosh_Jena_ : the documentation calls out that the migration script does not support versions later than 4.3.1 (see [1])Since you are on version 4.4.0 - hence the error.Please reach out to your Adobe point of contact (customer success manager to discuss the options)  [1]: 

@Nitesh-Chavan : you may want to post this to the Assets Community as this area is largely for AEM Guides questions and discussions

@davidl38471046 : which version of AEM Guides are you getting this issue? I tried with version 4.6, 5.0 and cloud latest - this is not reproducible. With more information we can try to reproduce the issue and suggest further.

@joshm19816095 : can you share a snippet of content that you authored?I tried using those links in same file, same paragraph without any word in between but the links work fine in the Native PDF output.I can try reproducing the problem with content you share

@1huntley : currently we support "ant" in the publishing procedures.But we plan to also support the option to use dita in future.

@DillipDi : If you deployed the custom profile through code, you may have to sync the JSON of property "profileConfigs" under your folder profile at "/var/dxml/folderprofiles/<profile-id>" Compare it with "profileConfigs" under "/var/dxml/folderprofiles/global-profile" Depending on from which versio...

@Arushi1991 : Tried the same steps with AEM Guides 4.6.0 (uuid) but this is not reproducible. I followed same steps but I do get the dialog in question at Step 5.Can you confirm if :1. the existing PDF (before download asset) had a UUID assigned to it already? (because the error [1] indicated in the...

You can raise a support ticket to get the timelines for any issues you want an update on. Or reach out to the CSAM for more details.

@ClydeG : that is what I observed too and I was suspecting as versionJson was introduced recently but documentation needs update here (for reference, the ticket for this documentation update is: GUIDES-26456)