Workflow instances stuck in running status
When workflow (WF) instances remain stuck in a running status for an extended period, open the WF model in Touch UI and compare it with CRXDE Lite. Make sure that the steps in the UI match the nodes in CRXDE Lite. Also check the self-hosting sync configuration and ÃÛ¶¹ÊÓƵ Launch Configuration by following the steps detailed in the Resolution section.
Description description
Environment
ÃÛ¶¹ÊÓƵ Experience Manager (AEM)
Issue
Workflow (WF) instances get stuck in a running status for more than a week.
The issue isn’t related to custom workflows, but to the configurations instead.
The status from Open History shows as COMPLETED, yet the WF remains stuck.
This problem can disrupt operations and delay processes that rely on the timely completion of workflows.
Resolution resolution
To resolve the issue of WF instances being stuck, use these methods:
-
Open the WF model in Touch UI and compare it with CRXDE Lite. Ensure that the steps in the UI match the nodes in CRXDE Lite. If discrepancies are found, recreate the WF model to ensure consistency.
-
In AEM as a Cloud Service, workflow models are stored as follows:
- OOTB workflow models:Â
/libs/settings/workflow/models/ - Custom workflow models:Â
/conf/global/settings/workflow/models/
- OOTB workflow models:Â
-
-
Follow these instructions to ensure proper configuration:
- Update archive paths within ÃÛ¶¹ÊÓƵ Data Collection environments.
- Rebuild the library with updated archive paths.
- Navigate to the required environment in AEM for self-host sync.
- Access ÃÛ¶¹ÊÓƵ Launch Configurations via Tools
>Cloud Services>ÃÛ¶¹ÊÓƵ Launch Configurations. - Locate and open the relevant launch configuration folder properties, then save and close them without making any changes.
- Publish the configuration once saved.
- Validate everything on CloudFront to ensure successful synchronization.
By following these steps, you should be able to address and resolve issues related to workflow instances being stuck in a running state.