Unable to create a workflow launcher in 6.5

AEMnewbie

23-09-2020

I am currently using AEM 6.5 and trying to create a new launcher by navigating to tools>workflows>launcher>create>add launcher . When i enter all the required data i see an error dialog with (Node with path /conf/global/settings/workflow/launcher/config does not exist.) 

Accepted Solutions (1)

Accepted Solutions (1)

BrianKasingli

MVP

24-09-2020

@AEMnewbie

I can definitely replicate your situation.

error-message.png

The resolution here is simple, to make sure the sling:Folder structure exists under /conf/global/settings/workflow/launcher/config (illustrated below):

jcr-structure.png

A simple fix is to create the exact structure above, as you see in the screenshot. In case if you've completely deleted the /conf/global folder, I've created a content package that you can download & install which has the exact setup as in the screenshot above; if you would like to re-setup the structure, you can go straight to http://localhost:4502/libs/granite/configurations/content/view.html/conf, to create the initial structure off /conf/global, but you must go into crx/de to complete the structure, by creating more sling:Folder nodes.

Good luck!

Answers (3)

Answers (3)

Vijayalakshmi_S

MVP

24-09-2020

Hi @AEMnewbie,

Can you try the below

  • Create a package with filter - /conf/global/settings/workflow/launcher/config (where there is no child nodes under config - Like empty launcher config filter)from one of your local instance
  • In your problematic instance,
    • Create a backup with same filter
    • Install the empty launcher config package built from other instance (the one from step 1)
    • Navigate to Workflow -> Launchers console -> Try creating one -> See if POST call to /libs/cq/workflow/launcher is 200

Arun_Patidar

MVP

24-09-2020

Could you please try creating nodes(sling:Folder) at conf /conf/global/settings/workflow/launcher/config

It may be required before creating launchers.

Anyways you have to deploy this launcher vai code so nodes needs to be created. so no harm to create manually.

 

Varun_Shakya

MVP

23-09-2020

  • Did the user have access to create Workflow launchers, check the permissions of the User.
  • Try creating the launcher in Vanilla AEM instance.

This seems the permission issue, if permissions are fine check the logs get more details and provide it here.