Issue Summary

Whenever a Confluence template has a broken macro "_confluenceADFMigrationUnsupportedContentInternalExtension_" on its content, the new pages created from this template via Automation will be marked as Legacy editor, despite the template being on "editor v2" (new editor).

This is likely caused by some issues when converting the template from legacy to new editor, or pasting the corrupted macro into the template, however it's not a problem when manually creating pages from that template - it only affects pages created via Automation.

Steps to Reproduce

1. Create a new template with the following content (may require tweak via DB if any additional param gets included):
   <p><ac:link><ac:link-body>Some Random Page/Blog URL Link</ac:link-body></ac:link></p>
2. Create an automation rule with "Publish new page" action and select the 'corrupted' template;

1. Trigger the automation rule;

Expected Results

New page is created as a regular new editor page

Actual Results

New page is created as "legacy editor" content

Workaround

Edit your template and ensure no occurrence of "_confluenceADFMigrationUnsupportedContentInternalExtension_" is present, or create the pages manually instead of using Automation.