Product Notices

On this page:

Known Issues

Known Issues in 2019.2.3 Maintenance Release

Workflow Builder/Engine Not Working as Expected

The 2019.2.3 maintenance release introduced a startup issue for some deployments. It was discovered that when a custom app or adapter failed to compile on startup, Workflow Builder/Engine did not work as expected.

This publication should help determine if your deployment is affected.

How to Recognize this Issue

The main symptom of this issue is the Workflow Builder only displaying two (2) apps.

Workflow Builder

After restarting the Workflow Builder, many additional apps will appear in Workflow Builder, but tasks will remain indefinitely in the running state.

This issue can occur in one of two ways:

  1. An application or adapter fails to load at startup.

    • This is the most frequently-observed condition; it is triggered by an app or adapter which fails to compile.

    • To identify this condition, navigate to the Settings > System page.

    • The following error log will display in the system journal:

      No health data recorded for Module:BrokenApp
    • To correct this condition, remove the failing app/adapter from the active profile and restart the platform.

  2. The permissions on the node_modules/@itential directory are incorrect.

    • This is a less likely condition; it is triggered by a combination of filesystem permissions and the reference_node feature in the Ansible Manager adapter.

    • In most cases, the IAP installer will set filesystem ownership and permissions to be writable by the Itential service account that is preventing this condition from occurring.

    • To confirm these permissions are still correct and have not been modified by external deployment scripts, run the following command:

      ls -l node_modules | grep "@itential$"
    • The directory should be owned and writable by the Itential service account:

      drwxr-xr-x. 52 pronghorn pronghorn  4096 Dec  1 20:11 @itential
    • To correct this condition, change the ownership and user write permissions of the node_modules/@itential folder back to its expected values:

      chown -Rf pronghorn:pronghorn node_modules
      chmod -Rf 755 node_modules

Note: Itential is actively working on resolving this issue and will update this notice once a permanent solution is available.


Error Importing a Workflow

Importing a workflow within the same major version of IAP should have no affect on importing. For example, if importing a workflow from 2019.1.4 to 2019.1.8, no impact to the import is expected since you are importing within the 2019.1 major version.

There are, however, exceptions when the workflows are imported from a newer maintenance release into an older one. For example, importing a workflow from 2019.1.8 to 2019.1.4 will fail with error.


In this instance the suggested workaround is to find the difference between the workflow schemas by using the following command:

diff workflow_2019.1.4.json workflow_2019.1.8.json

You can also use online tools like <> to find the difference between jsons.


Notice the "tags": [] key that is newly added to the workflow_2019.1.8.json. Removing this key from the workflow json will import the workflow in Workflow Builder successfully.

Apps or Adapters are Missing from Application Build

For IAP version 2019.3 and above, the workflow_builder application will encounter an exception when a task is accessed and the underlying app or adapter is missing from the application build. This happens when a workflow is built in an older version of IAP and then imported into the 2019.3 or higher versions.

With this type of exception, the workflow_builder application will hang and none of the tasks will be accessible. To resolve, refresh the webpage to make all the tasks accessible again.

In the image below, notice that the syncFrom task (added into version 2019.3) is retrieved and the underlying application is app-deviceManager (which is not part of the 2019.3 build).


Notice the error in the browser console:


Considering the task will never open, it becomes practically impossible to determine the assigned variables in a task. To get around this you will need to open the workflow document in your Mongo database.

Note: If you are still experiencing issues with workflows, please log a ticket with the Itential Service Desk. Be sure to provide all necessary information to reproduce the problem and the Itential Service Desk will help to address your issue.