Description of Problem:
In Autodesk Vault, lifecycle state changes can currently be performed even when related Job Processor jobs are still pending or processing for the same file. This can create situations where jobs fail because the file changes state before the workflow is completed.
Examples include:
- PDF/STEP/DWF publish jobs
- Synchronize Properties jobs
- Custom lifecycle automation jobs
A typical scenario is:
- User changes file state
- Vault creates one or more Job Processor jobs
- User immediately changes the file to another state
- Pending jobs fail because the file is no longer in the expected state, revision, permission context, or is no longer the Tip version
This creates unnecessary errors in the Job Queue, due to Non-Tip version issues, and makes it harder to identify real problems.
Suggested improvement:
Add an optional lifecycle setting or transition rule that:
- Checks for pending Job Processor jobs on the file
- Either warns or blocks the state change until jobs are completed
Possible options:
- Allow transition anyway
- Show warning only
- Block transition if jobs exist
- Block only for specific job types
- Showing active/pending jobs directly in the state transition dialog
Benefits:
- Reduces unnecessary failed jobs
- Cleaner Job Queue
- More reliable lifecycle workflows
- Prevents race conditions between lifecycle changes and automation
This would improve robustness for both standard Vault workflows and advanced automated environments using custom integrations.
