Workflow removed removing workflow instances newer than passed date

[tb7032]

Required Information

• AEM Version, including Service Packs, Cumulative Fix Packs, etc: AEM 6.3 / AEM 6.4__
• ACS AEM Commons Version: 3.17_
• Reproducible on Latest? yes

### Expected Behavior

Workflow remover should respect the 'Workflows older than' argument when deleting running workflow instances.

### Actual Behavior

Workflow instances newer than the passed date appear to get deleted.

### Steps to Reproduce

• Start clean AEM 6.3 / 6.4
• Install latest ACS Commons
• Start a couple of workflows that will stay in running state - ie a couple of Request For Activation worklfows (against any pages or assets).
• Confirm that the workflows are visible and showing as running in the workflow console
• Open workflow remover and select to remove:
  ** Status: Running
  ** Workflows older than: any date before the date the workflows started above (ie 72 hours ago
• Click 'Remove Workflows'
• Refresh workflow console and notice that the workflows started above were removed, despite apparently not meeting the passed criteria.

Links

n/a

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[vaibhav26sharma]

@davidjgonzalez @justinedelson I am also facing this. Can you please help here? All the workflow instances get removed without respecting Workflows older than criteria.

[vaibhav26sharma]

@davidjgonzalez In the meantime, can you please point me to the code so that I can debug and try to add an intermediate fix?

[pa-stef]

I, also get this bug.
I guess the problem is here
https://github.com/Adobe-Consulting-Services/acs-aem-commons/blob/acs-aem-commons-3.19.0/bundle/src/main/java/com/adobe/acs/commons/workflow/bulk/removal/impl/WorkflowInstanceRemoverImpl.java****
line 279
final Calendar startTime = properties.get(PN_STARTED_AT, Calendar.class);
PN_STARTED_AT has to be startTime

[davidjgonzalez]

This should be fixed via: #1793