Troubleshooting the K2 Workflow Importer

If errors or partial successes occur during workflow import, review the conversion.log file located at:
C:\Program Files\K2\ServiceBroker\Conversion\Logs
This log provides details that can help you identify the cause of the issue.

Use the following troubleshooting guidance to help diagnose and resolve common issues encountered during workflow packaging or import.

Q: No workflows are packaged from a list or library

A: The list or library contains only draft workflows. At least one workflow must be published before the extraction script can package it. Publish a workflow and run the script again.

Q: The extraction script fails or stops unexpectedly

A: No .nwf workflow files were found in the extracted package. Ensure that the source contains valid workflow files before running the script.

Q: The System folder is not visible in the Designer

A: The System Objects category is hidden by default. At the bottom of the Designer window, click (All) next to Show and enable System Objects.

Q: Errors or warnings appear in the imported workflow

A: Unsupported steps are replaced with placeholders and require additional configuration, or some mappings were not created during import. See the Post import section for more information.

Q: Category ID not found error in Swagger UI.

A: The catId value is incorrect or empty. In the Designer, select the category again and check the number after category&catid= in the URL. Use that value in the Swagger UI.

Q: Path not found error in Swagger UI.

A: The path value is empty or does not exactly match the category name in the Designer. Enter the exact name, including capitalization and spacing.

The following known issues may affect branching, connectivity, and deployment of workflows after import into Nintex Automation K2. These issues must be fixed or reconfigured manually.

Ensure that the latest fix pack is applied before using the K2 Workflow Importer to benefit from the most recent fixes, some of which may address the known issues listed below.

  • Issue:
    Imported workflows that contain a Yes/No variable fail to deploy.
    Resolution:
    Edit the Yes/No variable and select True, then False (or vice versa), and click OK.
  • Issue:
    Imported workflows that contain an Action Set step cause all branching after the step to fail and detach from the workflow.
    Resolution:
    Reconnect the detached steps of the workflow to the relevant Action Set placeholder manually.
  • Issue:
    Type error when reading Internal Push.
    In rare cases, the error "Type error: Cannot read properties of undefined (reading 'internalPush')" occurs. When this error occurs, the workflow becomes unusable.
    Resolution:
    No workaround is currently available. Rebuild the workflow manually in the workflow designer.
  • Issue:
    In some instances, deployment fails with error "Specify a valid name for the workflow before you deploy". There may be hidden special characters in the workflow name even though it may look fine.
    Resolution:
    Rename the workflow.
  • Issue:
    Imported workflows containing a Request Review step cause all branching after the Request Review step to fail and detach from the workflow.
    Resolution:
    Reconnect detached steps of the workflow to the relevant place holder manually.
  • Issue:
    If the workflow description is too long, deployment may fail with a database error.
    Resolution:
    Shorten or remove the workflow description.
  • Issue:
    Missing UI localization.
    Translation support for the Workflow Importer UI is not currently available. It is currently in English only.
  • Issue:
    Path vs catId limitations.
    When importing site workflows using Swagger UI, both path and catId are supported. However, path resolution fails if a folder name contains a special character. For example .FolderName.
    Resolution:
    Use catId instead of path to avoid possible path or folder name issues.
  • Issue:
    No error message on invalid SharePoint site URL.
    When an invalid SharePoint site URL is entered in the K2 Workflow Importer UI, the Workflow Importer will attempt to load it but no error message is displayed when it fails.
    Resolution:
    Ensure that you enter a valid SharePoint site URL.
  • Issue:
    Error or warning indicators may not appear on some unconfigured steps. However, the browser console displays an error identifying the affected step when a deployment is attempted.
    Resolution:
    Attempt to deploy the workflow, then review the browser console to identify the affected step and configure it accordingly.