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
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 ...
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
Hi @Sanket_Kumbharkhane , Thanks for your reply. We have set below
config for launcher:Event type: ModifiedNodetype: nt:unstructuredpath:
/content/xxxxxxxxxxx/jcr:content/par/uploadexcelworkflow is set as a
"simple notification step.workflow"Runmode : author & publish (Tried
with only PUBLISH also) Launcher works fine on author instance.
Thanks,Santhosh
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.corecom.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 ...
