Known Issues and Workarounds
- Issue #45664: Playbooks that are already pushed on the Tenant node will not be replaced if these playbooks have been moved to a different collection on the Master node.
To replace the playbooks on the tenant node, you must delete the existing collection, which contains the playbook that you want to replace, on the Tenant node.
- Issue #46368: Parent playbooks whose child playbooks contain the "Trigger Tenant Playbook" step, will remain in the Awaiting stage indefinitely if the parent playbook requires some input or response from the child playbook. For example, if you have a parent playbook that has called a child playbook that requires some response from a tenant or if that tenant cannot be reached, then the parent playbook will remain in the Awaiting stage indefinitely till there is some response from the child playbooks.
Currently, there is no workaround for this issue.
- Issue #78595: The master node gets stuck during the "Publish" operation and displays the "Publish initiated. Awaiting response from tenant" after changing the MMD at a tenant node.
This issue occurs when the "Publish" operation from the master node to a tenant node fails due to any reason such as, changing the type of a field from "string" to "integer" that will result in failure of the "Publish" operation.
To resolve this issue, refresh the browser window which enables the Revert All button. Click Revert All to revert all the changes made after which you will be able to use the system as before the "Publish" operation.