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
BedrockMission!

Learn More

View all

Sign in to view all badges

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

Avatar

Avatar
Validate 1
Level 2
santhoshd
Level 2

Likes

4 likes

Total Posts

5 posts

Correct Reply

1 solution
Top badges earned
Validate 1
Boost 3
Boost 1
Affirm 1
View profile

Avatar
Validate 1
Level 2
santhoshd
Level 2

Likes

4 likes

Total Posts

5 posts

Correct Reply

1 solution
Top badges earned
Validate 1
Boost 3
Boost 1
Affirm 1
View profile
santhoshd
Level 2

26-02-2021

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

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Validate 1
Level 2
santhoshd
Level 2

Likes

4 likes

Total Posts

5 posts

Correct Reply

1 solution
Top badges earned
Validate 1
Boost 3
Boost 1
Affirm 1
View profile

Avatar
Validate 1
Level 2
santhoshd
Level 2

Likes

4 likes

Total Posts

5 posts

Correct Reply

1 solution
Top badges earned
Validate 1
Boost 3
Boost 1
Affirm 1
View profile
santhoshd
Level 2

08-04-2021

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

Answers (6)

Answers (6)

Avatar

Avatar
Boost 500
MVP
Vijayalakshmi_S
MVP

Likes

500 likes

Total Posts

637 posts

Correct Reply

211 solutions
Top badges earned
Boost 500
Give Back 50
Give Back 5
Ignite 10
Ignite 5
View profile

Avatar
Boost 500
MVP
Vijayalakshmi_S
MVP

Likes

500 likes

Total Posts

637 posts

Correct Reply

211 solutions
Top badges earned
Boost 500
Give Back 50
Give Back 5
Ignite 10
Ignite 5
View profile
Vijayalakshmi_S
MVP

03-03-2021

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. 

Avatar

Avatar
Validate 1
Level 2
santhoshd
Level 2

Likes

4 likes

Total Posts

5 posts

Correct Reply

1 solution
Top badges earned
Validate 1
Boost 3
Boost 1
Affirm 1
View profile

Avatar
Validate 1
Level 2
santhoshd
Level 2

Likes

4 likes

Total Posts

5 posts

Correct Reply

1 solution
Top badges earned
Validate 1
Boost 3
Boost 1
Affirm 1
View profile
santhoshd
Level 2

03-03-2021

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

Avatar

Avatar
Boost 500
MVP
Vijayalakshmi_S
MVP

Likes

500 likes

Total Posts

637 posts

Correct Reply

211 solutions
Top badges earned
Boost 500
Give Back 50
Give Back 5
Ignite 10
Ignite 5
View profile

Avatar
Boost 500
MVP
Vijayalakshmi_S
MVP

Likes

500 likes

Total Posts

637 posts

Correct Reply

211 solutions
Top badges earned
Boost 500
Give Back 50
Give Back 5
Ignite 10
Ignite 5
View profile
Vijayalakshmi_S
MVP

02-03-2021

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

 

 

Avatar

Avatar
Validate 1
Level 2
santhoshd
Level 2

Likes

4 likes

Total Posts

5 posts

Correct Reply

1 solution
Top badges earned
Validate 1
Boost 3
Boost 1
Affirm 1
View profile

Avatar
Validate 1
Level 2
santhoshd
Level 2

Likes

4 likes

Total Posts

5 posts

Correct Reply

1 solution
Top badges earned
Validate 1
Boost 3
Boost 1
Affirm 1
View profile
santhoshd
Level 2

02-03-2021

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

Avatar

Avatar
Validate 1
Level 2
santhoshd
Level 2

Likes

4 likes

Total Posts

5 posts

Correct Reply

1 solution
Top badges earned
Validate 1
Boost 3
Boost 1
Affirm 1
View profile

Avatar
Validate 1
Level 2
santhoshd
Level 2

Likes

4 likes

Total Posts

5 posts

Correct Reply

1 solution
Top badges earned
Validate 1
Boost 3
Boost 1
Affirm 1
View profile
santhoshd
Level 2

01-03-2021

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

Avatar

Avatar
Give Back
Level 4
Sanket_Kumbharkhane
Level 4

Likes

46 likes

Total Posts

50 posts

Correct Reply

20 solutions
Top badges earned
Give Back
Boost 5
Boost 3
Boost 25
Boost 10
View profile

Avatar
Give Back
Level 4
Sanket_Kumbharkhane
Level 4

Likes

46 likes

Total Posts

50 posts

Correct Reply

20 solutions
Top badges earned
Give Back
Boost 5
Boost 3
Boost 25
Boost 10
View profile
Sanket_Kumbharkhane
Level 4

26-02-2021

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