Workflow version error | Community
Skip to main content
A
Anonymous
October 16, 2015
Solved

Workflow version error

  • October 16, 2015
  • 2 replies
  • 3830 views

Hello,

A missing version error is being repeatedly logged in error.log. The model itself is not present under in /etc/workflow/models

13.11.2013 12:05:11.486 *ERROR* [0:0:0:0:0:0:0:1 [1384324511478] GET /libs/cq/workflow/content/inbox/list.json HTTP/1.1] com.adobe.granite.workflow.core.jcr.WorkItemAdapterFactory error adapting a class of type [{org.apache.jackrabbit.core.NodeImpl}] to type [{java.lang.Class}] com.adobe.granite.workflow.model.VersionException: Version 1.3 does not exist for /etc/workflow/models/test1/jcr:content/model
    at com.adobe.granite.workflow.core.jcr.WorkflowModelManager.getWorkflowModel(WorkflowModelManager.java:96)

Thanks,

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    Best answer by WillMc1

    Hi,

    This is happening because you have an active workitem for a model that has been deleted.  The easiest way to rectify this is to use the Workflow Maintenance MBean to remove the workflow instances for this model which no longer exists.

    go to http://localhost:4502/system/console/jmx/com.adobe.granite.workflow%3Atype%3DMaintenance

     

    and use the "purgeActive" and "purgeCompleted" operations and make sure to pass the model ID mentioned in the error above --> "/etc/workflow/models/test1/jcr:content/model"

    You can use the dry-run option to preview the changes before executing them.

    Will

    2 replies

    W
    Adobe Employee
    WillMc1Adobe EmployeeAccepted solution
    Adobe Employee
    October 16, 2015

    Hi,

    This is happening because you have an active workitem for a model that has been deleted.  The easiest way to rectify this is to use the Workflow Maintenance MBean to remove the workflow instances for this model which no longer exists.

    go to http://localhost:4502/system/console/jmx/com.adobe.granite.workflow%3Atype%3DMaintenance

     

    and use the "purgeActive" and "purgeCompleted" operations and make sure to pass the model ID mentioned in the error above --> "/etc/workflow/models/test1/jcr:content/model"

    You can use the dry-run option to preview the changes before executing them.

    Will

      PAGIDALAGURUKRISHNA
      Adobe Employee
      PAGIDALAGURUKRISHNAAdobe Employee
      Adobe Employee
      May 4, 2023

      Hey Team,
      I have similar issue 
      Our error log is flooded with errors like. The one below.

      We have deleted all workflows already, so there should not be any reference to any workflow - regardless of the version.

      This makes the logfile useless for debugging an actual issue.

      ---

      28.04.2023 06:00:02.888 [cm-p88556-e766328-aem-author-5dc9f86dbd-qxqqc] *WARN* [94.134.95.241 [1682661602745] GET /mnt/overlay/granite/ui/content/shell/header/actions/pulse.data.json HTTP/1.1] com.adobe.granite.workflow.core.jcr.WorkflowModelManager Workflow model does not exist: /var/workflow/models/datev-request-for-activation
      28.04.2023 06:00:02.890 [cm-p88556-e766328-aem-author-5dc9f86dbd-qxqqc] *WARN* [94.134.95.241 [1682661602745] GET /mnt/overlay/granite/ui/content/shell/header/actions/pulse.data.json HTTP/1.1] com.adobe.granite.workflow.core.util.NodeReader error loading model
      com.adobe.granite.workflow.model.VersionException: Version 1.27 does not exist for /var/workflow/models/datev-request-for-activation
      at com.adobe.granite.workflow.core.jcr.WorkflowModelManager.getWorkflowModel(WorkflowModelManager.java:117) [com.adobe.granite.workflow.core:2.1.100]
      at com.adobe.granite.workflow.core.WorkflowSessionImpl.getCachedModel(WorkflowSessionImpl.java:538) [com.adobe.granite.workflow.core:2.1.100]
      at com.adobe.granite.workflow.core.util.NodeReader.createWorkflow(NodeReader.java:328) [com.adobe.granite.workflow.core:2.1.100]

      Any help!

      Thanks in Advance!

       

      Regards,

      Guru Krishna

      N
      nsoria1
      Level 3
      July 19, 2023

      Hey @pagidalagurukrishna have you had any luck removing that workflow?

      Terms & ConditionsAccessibility statement

      Loading footer...