Our custom ECN lifecycle workflow is consistently getting stuck at the Review step in ENOVIA R2021x. The ECN reaches the review state but never progresses even after approvers complete their tasks. We’ve checked the lifecycle XML mapping and it looks correct - the signature requirements are defined and the route template is properly configured. The approval tasks are completing successfully in inbox, but the workflow agent doesn’t seem to be detecting completion and promoting the ECN to the next state. This is causing significant approval delays across multiple engineering projects. Has anyone experienced workflow agents not properly monitoring lifecycle state transitions?
Based on the symptoms you’re describing, this is likely a combination of issues across all three focus areas. Let me walk through the systematic solution:
Lifecycle XML Mapping Verification: Your lifecycle XML needs precise alignment with your route template. Open your ECN lifecycle XML definition and verify the signature requirements section matches exactly. The XML should specify:
- Correct role names (case-sensitive) that exist in your system
- Proper approval counts (minimum approvers required)
- Correct state names that match your policy definition
Common mistake: The XML references ‘Review’ state but your policy actually calls it ‘In Review’ - this mismatch prevents the agent from recognizing completion.
Role Permissions Analysis: The workflow agent runs under a system user context (typically ‘creator’ or a designated agent user). This user must have:
- Promote privilege on ECN type
- Read/Modify access to ECNs in Review state
- Execute permission on any triggers associated with state transitions
Verify the agent user permissions by logging in as that user and attempting to manually promote an ECN. If manual promotion fails, you’ve found your permission gap.
Workflow Agent Status Resolution: Navigate to System Admin > Agent Administration and check:
- Lifecycle Promotion Agent shows ‘Running’ status
- Last execution timestamp is recent (within last 15 minutes)
- No error messages in execution history
- Agent schedule is appropriate (should run every 5-10 minutes for responsive promotion)
If the agent is running but not processing your ECNs, check the agent filter settings. The agent might be configured to only process certain types or states, excluding your custom ECN lifecycle.
Diagnostic Steps:
- Enable detailed logging for the lifecycle promotion agent
- Review agent logs during the next execution cycle
- Look for specific error messages mentioning your ECN numbers
- Common log errors: ‘Signature requirements not met’, ‘Permission denied’, ‘Trigger execution failed’
Immediate Workaround: While investigating, you can manually promote stuck ECNs using the ‘Promote’ action if you have appropriate permissions. This unblocks critical engineering work while you fix the root cause.
Long-term Fix: Once you identify the specific issue (XML mismatch, permission gap, or agent configuration), document the correction and implement monitoring. Set up alert notifications if the lifecycle promotion agent fails or stops running. This prevents future occurrences of stuck workflows impacting project timelines.
This draft is based on general ENOVIA knowledge. It has not been verified against your specific version and environment. Practitioners: verify the steps and share your experience below.
First thing to check is whether your workflow agent is actually running. Go to the agent administration page and verify the lifecycle promotion agent shows as active and has recent execution timestamps. Sometimes agents get disabled after system maintenance or configuration changes without anyone noticing.
I’ve seen this when the signature requirements in the lifecycle XML don’t exactly match the route template configuration. Even small mismatches in role names or approval counts can cause the agent to think requirements aren’t met. Double-check that your XML specifies the same roles and approval thresholds as your route template. Case sensitivity matters too - ‘Design Engineer’ is different from ‘design engineer’ in the XML parser.
Check the agent execution logs for any error messages. The logs might show that the agent is running but encountering permission issues when trying to promote the ECN. The agent runs under a specific user context, and that user needs proper permissions to promote objects through lifecycle states. If the agent user lacks promote privileges, tasks will complete but state transitions won’t happen.
Another possibility is the trigger configuration on your lifecycle state. Each state can have triggers that must complete before promotion occurs. If you have a custom trigger on the Review state that’s failing silently, it would block promotion even though approvals are done. Review your lifecycle policy definition for any triggers attached to the Review state and verify they’re executing successfully. You can test this by temporarily removing triggers and seeing if promotion works.
Don’t overlook the route template status itself. If the route template is in a non-active state or has been modified after ECNs started using it, you can get stuck workflows. Verify that your route template shows as Active and hasn’t been edited since these ECNs were created. Sometimes people modify templates thinking it won’t affect in-flight workflows, but it absolutely can.
Check if you have any custom Java or MQL code that’s supposed to execute during the Review state transition. Custom promotion code can throw exceptions that prevent state changes but don’t always surface clearly in the UI. Look for any custom actions or programs associated with your ECN lifecycle and verify they’re not failing.