Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

Launchers not working in publish instance after update from 6.3 to 6.5

santhoshd
Level 2
Level 2

Hi All,

 

We have an issue where launchers are not getting triggered in publish instance but works fine on author instance. There are no errors in log files and we have also set loggers for below

 

com.adobe.granite.workflow.core

com.adobe.granite.workflow.core.launcher

 

but still there is no useful info. To rule out the permissions issue, we have provided RMCDR permission to all folders for workflow system users. 

On further digging, it seems the listener is not getting triggered on node modification (My assumption). We tried even with a simple OOTB workflow but still did not work. It works fine on author instance as stated previously. 

Does anyone have idea on this issue or what all things needs to be checked. Workflows are under  /var/workflow/models and settings under /conf/global/settings/workflow. 

 

com.adobe.granite.workflow.core.launcher.WorkflowLauncherListener

 

Thanks,

Santhosh

1 Accepted Solution
santhoshd
Correct answer by
Level 2
Level 2

Hi All- Thanks for your replies.

We have resolved the issue by cleaning up var/workflow/instances and etc/workflow/instances as there were running workflows and their modes has been mvoed under var or had been deleted. Hence we have deleted the server0 and server1 folder under var and etc instances which fixed the issue.

 

Thanks,

Santhosh

View solution in original post

0 Replies
Sanket_Kumbharkhane
Level 4
Level 4

Hi @santhoshd ,

can you please provide the basic configuration of your workflow launcher here? Also, can you also check the run modes assigned to the launcher?  Generally, to run both on Author & Publish, select or add 'Author & Publish' from run modes dropdown.

 

Thanks,

Sanket

santhoshd
Level 2
Level 2

Hi @Sanket_Kumbharkhane ,

 

Thanks for your reply.

 

We have set below config for launcher:

Event type: Modified

Nodetype: nt:unstructured

path: /content/xxxxxxxxxxx/jcr:content/par/uploadexcel

workflow is set as a "simple notification step.workflow"

Runmode : author & publish (Tried with only PUBLISH also)

 

Launcher works fine on author instance.

 

Thanks,

Santhosh

kautuk_sahni
Community Manager
Community Manager
@santhoshd, Thank you for sharing the answers with community. Keep assisting the AEM community. AEM Community needs SMEs like you.
Sanket_Kumbharkhane
Level 4
Level 4

Thanks for the reply @santhoshd , The basic configuration looks good and if the launcher is in an enabled state & the node has a primary type as "nt:unstrcutured", it should work. This is just another pointer from my side to double-check, it could possible that run modes are not properly set while AEM installation if you are trying it on local or dev.

As per adobe doc: 

When using one of the above run modes (author, publish, samplecontent, nosamplecontent), the value used at installation time defines the run mode for the entire lifetime of that installation. For these run modes, you cannot change them after installation.

 

@kautuk_sahni , the above-accepted solution is not an actual answer but addition of information to the actual question to debug.  Please correct. Thanks.

santhoshd
Level 2
Level 2

Hi @Sanket_Kumbharkhane ,

 

Thanks for the reply. Issue is seen in our Dev stage and Production publishers. We have also raised a day care but we are not able to fix the issue. It should be due to some OOTB functionality which is breaking the launchers as it is not working on publishers only across all instances. Please let me know if you have any idea on this.

 

Thanks,

Santhosh

Vijayalakshmi_S
Community Advisor
Community Advisor

Hi @santhoshd,

Can you confirm if you have workflow models available in /conf/global/settings/workflow/models(updated workflow model location starting 6.4) along with runtime location /var/workflow/models in publish instance. 

Ignore if you have already checked and it is available. 

Also, could you please share details on how you have updated workflows as part of upgrade from 6.3 to 6.5

 

 

santhoshd
Level 2
Level 2

Hi @Vijayalakshmi_S ,

 

I have verified that the workflow models are present under /conf/global/settings/workflow/models. 

 

During 6.5 update we moved the workflows from old etc/workflow to var/workflow/models and launchers under conf/global/settings/ in AUTHOR only. We do not do anything specifically for publish workflows during upgrade. I also took the package from author with launcher and workflows and installed it on publishers. Still no luck.

 

Please let me know if there is any configs which we might have missed or specific to publish instances that needs to be added. Because we have checked all the old vs new updated workflow and launcher paths which works fine on author instances but not on publish.

 

Thanks,

Santhosh

Vijayalakshmi_S
Community Advisor
Community Advisor

Hi @santhoshd,

When you say that you moved from old /etc/workflow to /var/workflow, confirm if you did like below

When it is in the old location, 

  • Open the desired workflow model in the editor -> editor view in touch UI workflow model is -  /conf/global/settings/workflow/.. (as evident from the address bar)
  • Click on Sync (at the top right) in the model editor -> updates the run time workflow model, it writes to /var/workflow/models/.. 
  • Migrate all project specific workflows like this and test the workflow functionality. 
  • In the project code base -> content module -> package/include the models from both the locations and the corresponding entry in filter.xml (path of your workflow model from both /conf and /var)

In brief, it shouldn't be like direct copy from /etc to /var. Instead Sync from the model editor writes to new location. 

santhoshd
Correct answer by
Level 2
Level 2

Hi All- Thanks for your replies.

We have resolved the issue by cleaning up var/workflow/instances and etc/workflow/instances as there were running workflows and their modes has been mvoed under var or had been deleted. Hence we have deleted the server0 and server1 folder under var and etc instances which fixed the issue.

 

Thanks,

Santhosh

View solution in original post