hello,
I am also facing this issue (a rejected form can't be approved anymore while throwing this frozen error) and although I can imagine (haven't found it exactly yet) there is something missing in the workflow, I do not see how a change in workflow and redeployment can fix a running form? The version in which the issue is, is a lower version than the redeployed version in that case. Running forms are not updated with new workflow/rules etc due to a deployment.
Can you elaborate?
------------------------------
Ed Meiners
Wessanen Nederland Holding BV
------------------------------
Original Message:
Sent: 02-19-2026 06:46
From: Divya Verma
Subject: WFAssignment.Frozen error in Workflow
Hi Jan,
The error "WFAssignment.Frozen" typically occurs under the following conditions:
There are no active assignments, while the process status remains Running, or
A task does not resolve to any Actor, while the process is still in Running status.
In some cases, the issue is caused by an incorrect decision node and its transition conditions. After completion of an approval element, the transition logic may fail to return a valid next activity node. As a result:
No new assignment is created,
The process remains in Running state,
The system detects a deadlock situation and triggers the WFAssignment.Frozen error.
Resolution
To resolve this issue, please:
Validate all transition conditions associated with the decision/approval node.
Ensure that at least one valid next activity node is returned after the decision node/ transition condition/ approval action.
Confirm that proper Actor mapping is configured for the subsequent task.
Once the workflow logic is corrected and redeployed, the process should proceed without entering a Frozen state.
Thanks
------------------------------
Divya Verma
*Precisely Software Inc.
------------------------------