You can start exploring CMS headless use case and a best practice usage by reviewing the Mobile WKND project: Overview .

Do you use an editable template in Touch UI? If yes, you should leverage a layout component policy to allow your component in CF.

You can review WKND tutorial for header & footer creation: 7 - Header and Footer

You need to request a Classic Target account from Target Support. AEM is still using a Classic Target API to connect to Target. By default, Classic Target Account is not assigned when Tagert is provisioned to an organization.

What is your business case, that you need to disable indexes and force a traversal search? Traversal search will significantly affect performance and as a result, the AEM server might not responsive at all.

It seems like you are using new IMS to Target connection. The reason that XF exported as an HTML is a known limitation of the current implementation of IMS->Adobe IO -> Target connection. In order to be able to export to Target as XF you need to use an old (deprecated) way by employing a Target Clas...

"but the notification is just one" - it's expected. It starts a single workflow with multiple payloads by selecting a folder as a payload. There is no option to start multiple workflows for each asset in the payload folder.

Do you have a Dispatcher front end on those environments, where JSON call is failing? If yes, review the dispatcher rules and make sure that the call is nor denied.

If assets reside in the same folder, you can choose the folder itself as a payload destination.

Is it a Target via Adobe IO integration?If yes, you need to get to Experience Cloud Admin Console Admin Console From Product select Workspace -> Integration and add your Adobe IO integration with Approver product role