I found an issue with Workflow where Workflow State and Workflow Action become inconsistent if the state is reverted back to a previous step.
Observed behavior:
- The Workflow State changes correctly to the reverted state.
- However, the Workflow Action still remains assigned to the user who triggered the previous state transition.
- No new Workflow Action is created for the user(s) responsible for the current (reverted) state.
It seems that the system does not properly clear or regenerate Workflow Actions when a document’s state is moved back to an earlier state.
Example Workflow Setup
- States: Draft → Waiting for Approve 1 → Completed
- Transitions:
• From Draft, action “Submit” → moves state to Waiting for Approve 1
• From Waiting for Approve 1, action “Rework” → moves state back to Draft
Expected Behavior
When following the above scenario, there should be 3 Workflow Actions in total:
- Draft → Waiting for Approve 1 (completed)
- Waiting for Approve 1 → Draft (completed)
- A new Draft action created, waiting for the responsible user to continue
Actual Behavior
- The first action (Draft → Waiting for Approve 1) is marked as Completed (correct).
- The second action (Waiting for Approve 1 → Draft) remains Open instead of being marked as Completed.
- No new Workflow Action is created for the Draft state after rework.
Impact
As a result, users are stuck because there is no Workflow Action assigned for the reverted state. The Workflow State shows correctly as Draft, but the Workflow Action list is inconsistent and prevents further progress.
