AEM 6.4 WorkflowStatus Api returning false for running workflow

[vipins5188]

Hi All,

We are facing an issue with WorkflowStatus api to get current wf status of a resource.

It works fine when we start a workflow and get running status it return true but when we deploy our code again even though workflow still in running condition ,the api returns us as false.

resource.adaptTo(WorkflowStatus.class).IsInRunningWorkflow(true);

This issue only happening if we redeploy our code.

Any idea what can cause this issue ?? What is happening during bundle deployment which makes this api return status as false even though workflow still running ??

Thanks

[arunpatidar]

Hi,

Not sure why this happening, can you try with alternative method, to check if payload is not part of any workflow?

resource.adaptTo(WorkflowStatus.class).getWorkflows(true).isEmpty();

[vipins5188]

Hi Arun,

I tried with resource.adaptTo(WorkflowStatus.class).getWorkflows(true).isEmpty(); to check if its part of any workflow but this one also return me with an empty list.

As soon as i send page for workflow these methods returns correct status but if i deploy the code after workflow started these are sending me false status, any idea why ??/

[smacdonald2008]

Typically code is deployed prior to running a workflow. If it works when code is deployed, there is no issue.

[arunpatidar]

Hi,

Could you please explain where you are checking the status? It is inside service or WCMUsePojo/Model or workflow step?

And when you restart the bundle or redeploy then if you check again, then what happened to status.

Let me try same with servlet.

[vipins5188]

Hi Arun,

i am implementing custom  ResourceStatusProvider to get status of particular resource to show on page,for this i am getting an issue with status so i implementated a servlet just to check what status i am getting.  There i found that Workflow Status is not properly coming. After deploying code status of Workflow is active and its in running condition . I checked the same under /var/workflow/instances

[arunpatidar]

For me its working for existing workflow as well.

Servlet - aem63app-repo/CheckPageWorkflowServlet.java at master · arunpatidar02/aem63app-repo · GitHub

[vipins5188 · Accepted solution]

Thanks Arun Patidar  smacdonald2008 for your response.

I have got the solution for this issue, actually we are maintaining Adobe Granite Workflow Service configuration and adding one custom group to superuser property, which was removing OOTB workflow service user from superuser group that was causing this issue. By removing that configuration, it worked fine.