Question:

Why does a User encounter a Server Error when attempting to complete a Document Workflow Task with minor versions? 

Answer:

The State into which the Workflow moves the document may contain Entry Actions that cannot be completed.

Example:

A document goes through an Approval workflow. Many minor versions are created, and when the document reaches version 0.56, the workflow is ready to complete and move the document into the Approved State. The User attempts to complete the final Workflow Task to move the document, but Vault presents them with a server error when they attempt to do so.

This can occur when there is an Entry Action for a Document State that cannot be executed. In this example, the document Lifecycle contains an Entry Action to delete all Minor Versions of a document upon its entry into the Approved state

Vault presents this user with the Server Error because there are minor versions of the Document that still reference other object records and/or documents. Removing the reference from the minor version of the document allows the user to proceed into the Approved state.

This is one example of an Entry Action preventing a document workflow from completing. Other Entry Criteria on a given Lifecycle State may also cause the same error, making it important for Administrators to be aware of the criteria that govern a document's ability to enter states.

Related Documentation:

Vault Help Documentation: Defining Document State Entry Criteria