We’re experiencing a blocking issue with our release approval workflow in Rally. When features reach the manager approval stage, the workflow state transition completely halts and artifacts remain locked indefinitely.
The problem manifests specifically during release cycles when multiple features need manager sign-off simultaneously. The approval event mapping appears correct in our workflow configuration, but the state simply won’t advance past the manager approval node. We’ve verified that role-based permissions are properly assigned to the manager group.
WorkflowState: PENDING_MANAGER_APPROVAL
ArtifactLock: true
ApprovalEvent: manager_review_complete
ExpectedTransition: APPROVED → not triggering
This is blocking our entire release pipeline as downstream automation depends on these approvals completing. Has anyone encountered similar workflow state transition issues with artifact locking mechanisms?
I’ve identified the root cause of this issue through similar cases. Your problem involves multiple interconnected workflow mechanics that need systematic resolution.
Workflow State Transitions: The state machine isn’t advancing because the transition condition is checking for artifact lock release BEFORE processing the approval. You need to modify your workflow definition to release locks as part of the approval event handler, not after the transition completes.
Role-Based Permissions: Verify that managers have both ‘Approve Release’ AND ‘Modify Locked Artifacts’ permissions. The transition requires both - one to approve, one to unlock during the state change.
Artifact Locking Mechanism: Implement explicit lock management in your workflow:
// In approval event handler
artifact.releaseLock()
approvalEvent.process()
workflowState.transition("APPROVED")
Approval Event Mapping: Your event mapping needs to include lock release as a pre-transition action. Update your workflow configuration to add a pre-transition hook that clears artifact locks before attempting state changes.
The key is ensuring lock release happens synchronously with the approval event, not as a separate asynchronous operation. This prevents the race condition where the state transition attempts to proceed while the artifact is still locked. Test with a single feature first to verify the corrected sequence before processing bulk approvals.
Also review your workflow processing queue settings - if events are backing up during high-volume release cycles, you may need to increase the concurrent processing limit to prevent the delays you’re experiencing.
I’d recommend examining the workflow event queue. If approval events are queuing up faster than they’re being processed, you’ll see exactly this symptom - events fire but transitions don’t complete. You might need to adjust your workflow processing settings or add explicit ordering to how approval events are handled during high-volume release cycles.
We’re using a customized workflow that extends the default approval process. I checked the workspace-level permissions and they look correct - managers have the ‘Approve Release’ permission enabled. The strange part is that the approval event fires (we can see it in the activity log) but the state transition doesn’t execute. The artifact remains locked even after the approval event completes.
Are you using custom workflow rules or the default Rally approval process? We had a similar issue where role-based permissions were configured at the project level but not at the workspace level, which caused approvals to fail silently. The workflow state would show pending but never transition because the permission check was failing upstream.
I’ve seen this behavior before. Check if your approval event mapping has the correct trigger conditions defined. Sometimes the workflow engine doesn’t recognize the approval event if there’s a mismatch between the event name and what the workflow state expects. Also verify that the artifact locking mechanism isn’t preventing the state transition due to concurrent modification attempts.
This sounds like a race condition in the workflow state machine. When multiple features hit the approval stage simultaneously, the artifact locking mechanism might be creating deadlocks. Check your workflow transition rules for any conditional logic that could be evaluating to false when concurrent approvals are processed. We resolved a similar issue by implementing sequential approval processing instead of parallel.