Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Reviewing command-line migration logs and work item status

Updated on August 25, 2021

After migrating a product or application, view the migration results and troubleshoot any errors.

The Log messages include the following information:

  • Time stamp – The date and time of the migration request
  • Message – The results of creating the .zip archive (including the .zip file’s name), the covered work items, and their IDs

The Return messages indicate whether the connection was successful. Review the messages for detailed information about each work item.

  1. Click Destinations to review the status of each work item:
    • If the connection succeeded and the file was successfully loaded onto the server, the work item status moves from Pending to Resolved. A delay of a few minutes might occur while the .zip file is retrieved from the temp directory and its contents are imported. When the upload finishes, the status updates to Resolved.
    • If the connection failed or if a system error prevented the file from loading, the work item status remains Pending.
  2. Click the Work ID link to display log messages.
  3. If the connection failed, click the work flow link to resolve the issue. Then, either retry the connection to the server, or click Cancel to withdraw and resolve the work item.
  4. Optional:

    If you imported an application that was on an earlier version of Pega Platform, edit the application definition to include the current built on version.

    For more information about editing the application definition, see Changing the built-on version of an application to the current version.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us