Installed process flows not working as expected
Last updated
Last updated
You've installed a process flow from the Patchworks marketplace via a or via the section. When you run the process flow it either fails or does not work as expected.
When a blueprint or a process flow is installed, it usually includes dependencies such as connectors, scripts, caches, etc. If a dependency fails to install or has not been deployed correctly, this can cause associated process flows to fail or give unexpected results.
Check the following:
Once a blueprint or process flow has been installed from the marketplace, a series of confirmation messages is displayed - one message for each component.
Typically these are 'success' messages, but occasionally you may see a failure for one or more components. These messages are displayed briefly and then cleared however, you can review them later from your .
If any part of the installation is shown to have failed, you can install the or again.
Installation instructions for Patchworks blueprints and process flows include some post-install setup steps - these must be completed before any associated process flows will run correctly. Double-check these steps to ensure that all required setup has been completed:
Any custom scripts associated with a Patchworks blueprint or process flow are installed and deployed as part of the installation process. However, if an installed process flow is not working as expected, it's a good idea to check that all required scripts are deployed. To do this, follow the steps below.
Step 1 Select scripts from the left-hand navigation menu:
Step 2 Check the deployment status column for listed scripts - you're looking for any that show as un-deployed:
Step 3 Click the name of the first un-deployed script:
Step 4 Scroll down and click the save and deploy button:
Step 5 Repeat these steps for any other scripts that need to be deployed.