In AEM as cloud.
Up until Tuesday, October 28th, all our custom workflows, including those with dynamic participant steps, were functioning as expected. However, starting from October 31st, we noticed that these workflows are failing to complete at the user-input steps in both the DEV and QA environments. Interestingly, we did not observe any project-specific errors in the logs.
It's worth noting that this issue is not occurring in our Stage and PROD environments, where all workflows are running smoothly. After some investigation, we found a disparity in the SDK versions being used across the environments. In DEV and QA, the SDK version is 2025.10.23122.20251023T134343Z, whereas in Stage and PROD, the SDK version is 2025.10.22943.20251009T135918Z.
Moreover, replicating the issue locally with the SDK version 2025.10.23122.20251023T134343Z yielded the same problem.
Please suggest any quick actions from our side.
Solved! Go to Solution.
Topics help categorize Community content and increase your ability to discover relevant content.
Views
Replies
Total Likes
Hello @tejaswi_aem
This behavior has been confirmed to be caused by a regression introduced in the AEMaaCS Release 2025.10.23122.
The issue has been acknowledged and worked upon by Adobe.
Engineering team has already performed a global rollback to the previous stable build across all affected customer environments.
Following this rollback, the Workflow Participant / User Input steps should now function as expected in AEMaaCS Environments
Views
Replies
Total Likes
Hello @tejaswi_aem
If the behaviour is replicable locally, please report the same to AEM Support
Views
Replies
Total Likes
Hello @tejaswi_aem
This behavior has been confirmed to be caused by a regression introduced in the AEMaaCS Release 2025.10.23122.
The issue has been acknowledged and worked upon by Adobe.
Engineering team has already performed a global rollback to the previous stable build across all affected customer environments.
Following this rollback, the Workflow Participant / User Input steps should now function as expected in AEMaaCS Environments
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies