Server Administration > Change Packages for SCM > Change Package Reviews Overview > Change Package Review Workflow > Intermediate States of a Change Package
  
Intermediate States of a Change Package
A change package moves to an intermediate state if any of the changes are not committed to the repository because of reasons like broken connectivity with the server or server crash. Windchill RV&S indicates failure to commit to the repository and allows you to reattempt or discard the changes.
Change Package State
Details
Committing Entries
Intermediate state denoting that the proposed changes are ready to be committed in Windchill RV&S and source repositories. In case of any issue with the server, the Discard, Submit or Accept operation for a change package can be reattempted in this state.
Entries in Sync
State denoting that the change package is not closed, but all submitted changes are accepted by the reviewers, if required, and committed to the repository. The creator can Close or Reopen the change package in this state.
CommitFailed
State signifying that the pending changes could not be committed to the repository. Discard, Submit or Accept operation for a change package can be reattempted in this state. For more information, see Intermediate States of a Change Package.
* 
A reviewer can Accept a change package which is in the Accepted, Committing Entries, or CommitFailed state without following the standard review process mentioned under Change Package Review Workflow.
The following figure indicates the workflow of a change package through intermediate states.