Incorrect workflow count and unhealthy system status in AEMaaCS
Adobe Experience Manager as a Cloud Service (AEMaaCS) displays incorrect running or completed workflow counts, which causes the system health indicator to show an unhealthy status. This issue occurs due to a known product bug, and the displayed count typically auto‑corrects after several days. To resolve the issue, verify workflow instances and monitor the UI until the values are correct.
Description description
Environment
Adobe Experience Manager as a Cloud Service (AEMaaCS)
Enhanced Issue/Symptoms
- Even after running workflow purge, the workflow count in the AEMaaCS UI displays an unusually high number of running or completed workflow instances.
- The workflow console shows no matching workflow instances, creating a clear mismatch with the UI‑reported totals.
- The system health indicator reports an unhealthy status because the incorrect workflow count affects the displayed system metrics.
Resolution resolution
Follow the steps below to address the issue:
-
Check the Workflow console
/libs/cq/workflow/admin/console/content/instances.htmlto confirm there are no running workflows.For completed workflows, check
/libs/cq/workflow/admin/console/content/archive.html. -
Run a query for running or completed workflows to verify the latest count.
-
If the UI shows an incorrect count even though no workflows are running or completed, note that this is a known product limitation-GRANITE-64222
-
Monitor the Workflow UI for a few days until the counts auto‑correct, and confirm the system health status returns to healthy.
Note: The workflow count displayed in the UI doesn’t reflect the actual number of running or completed workflows and should auto‑correct over time.
Related reading
Administering Workflow Instances in the AEM as a Cloud Service User Guide