AEM 6.4 WorkflowStatus Api returning false for running workflow | Community
Skip to main content
vipins5188
vipins5188
Level 3
Dec 9, 2018 9:19 PM UTC
Solved

AEM 6.4 WorkflowStatus Api returning false for running workflow

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

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    vipins5188
    vipins5188Accepted solution
    Level 3
    Dec 12, 2018 12:32 AM UTC

    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.

    View reply

    7 replies

    vipins5188
    vipins5188AuthorAccepted solution
    Level 3
    Dec 12, 2018 12:32 AM UTC

    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.

    Translate
    arunpatidar
    arunpatidar
    New Participant
    Dec 10, 2018 3:46 PM UTC

    For me its working for existing workflow as well.

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

    Translate
    Arun Patidar
      vipins5188
      vipins5188Author
      Level 3
      Dec 10, 2018 3:43 PM UTC

      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

      Translate
      arunpatidar
      arunpatidar
      New Participant
      Dec 10, 2018 3:25 PM UTC

      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.

      Translate
      Arun Patidar
      smacdonald2008
      smacdonald2008
      Level 10
      Dec 10, 2018 3:02 PM UTC

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

      Translate
      vipins5188
      vipins5188Author
      Level 3
      Dec 10, 2018 2:54 PM UTC

      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 ??/

      Translate
      arunpatidar
      arunpatidar
      New Participant
      Dec 10, 2018 6:23 AM UTC

      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();

      Translate
      Arun Patidar
      Terms & ConditionsAccessibility statement

      Loading footer...