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

AEM workflow instances and archive not always displayed

Avatar

Avatar
Ignite 1
Employee
sean_gubler
Employee

Likes

0 likes

Total Posts

2 posts

Correct Reply

0 solutions
Top badges earned
Ignite 1
View profile

Avatar
Ignite 1
Employee
sean_gubler
Employee

Likes

0 likes

Total Posts

2 posts

Correct Reply

0 solutions
Top badges earned
Ignite 1
View profile
sean_gubler
Employee

09-08-2019

One of our Adobe tech partners has asked the following....

I’m currently developing an Osgi module for AEM. We are currently using AEM 6.3.3.2 and I’m experiencing an unexpected behavior while using workflows.

Performed steps

1. Create a simple workflow model with only one process step. The process step was implemented by me and packaged in the Osgi bundle

2019-08-09_15-18-25.png

2. Launch the workflow

Expected behavior

The workflow should be displayed in Workflow instances while running and in Workflow archive after a successful completion

Current behavior

I can see from logs that my custom workflow process step ran correctly and that the workflow is displayed in Workflow instances while running, but once completed it is neither in Workflow archive nor in Workflow failures. Moreover this misbehavior is not systematic because sometimes it happened that it was not even displayed in Workflow instances.

Here I’ve captured the node corresponding to the completed instance on CRXDE, which correctly shows the workflow as completed

2019-08-09_15-20-08.png

Additional information

In a local instance of AEM 6.4, this issue is not happening, even if I found on the web some users complaining about a similar issue in AEM 6.4.2 https://forums.adobe.com/thread/2497482

In the logs I’ve found a few exceptions like the ones in the attached file. I don’t know if there’s a correlation.

Can you please support and confirm that this is an issue?

Replies

Avatar

Avatar
Give Back 5
Employee
Andrew_Khoury
Employee

Likes

75 likes

Total Posts

93 posts

Correct Reply

33 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back 10
Give Back
Boost 50
View profile

Avatar
Give Back 5
Employee
Andrew_Khoury
Employee

Likes

75 likes

Total Posts

93 posts

Correct Reply

33 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back 10
Give Back
Boost 50
View profile
Andrew_Khoury
Employee

09-08-2019

I searched our bug tracker and I couldn't find a matching issue.  However, I have seen some cases where somebody tries to terminate a workflow during an AEM restart and it picks up the Sling POST servlet instead of the workflow servlet.  In these cases this node gets corrupted: /var/workflow/instances

To see if this is the cause and fix it, do the following:

1. Go to http://aemhost:port/crx/de/index.jsp#/var/workflow/instances and log in as admin

2. Check the Properties tab for the properties of the node.  Make sure these properties are set, if they are not then set them:

sling:resourceType=cq/workflow/components/instances

jcr:title=Instances

Avatar

Avatar
Coach
MVP
Arun_Patidar
MVP

Likes

1,429 likes

Total Posts

3,300 posts

Correct Reply

937 solutions
Top badges earned
Coach
Contributor 2
Ignite 10
Give Back 700
Boost 1000
View profile

Avatar
Coach
MVP
Arun_Patidar
MVP

Likes

1,429 likes

Total Posts

3,300 posts

Correct Reply

937 solutions
Top badges earned
Coach
Contributor 2
Ignite 10
Give Back 700
Boost 1000
View profile
Arun_Patidar
MVP

10-08-2019

you can also check -

is workflow transient?

Is workflow purging running frequently?