Select a Snaplex to Run your Pipelines

You can configure which Snaplex a Pipeline, Task, API/Proxy will use in one of the following ways:

With a Pipeline open in Designer, you can select from the Snaplex drop-down menu a Snaplex on which the Pipeline should run.

Only Snaplexes placed in the global shared folder are accessible in APIM. If a Snaplex is in a project or Project Space shared folder, then it does not display in the APIM Snaplex picker.

When you configure a Scheduled or Triggered Task, you can select the Snaplex to run the Pipeline.
When using the Pipeline Execute Snap,
- The Pipeline Execute Snap has a Snaplex field that specifies the child Pipeline’s Snaplex. leave the field blank.
- As an alternative, use the pipe.plexPath expression to ensure that the child Pipeline runs on the same node as the parent.
- if you specify a different Snaplex to run a child Pipeline, then the input documents and Pipeline parameters are passed through the Control Plane using encrypted transport to a node in the designated Snaplex.

You can improve performance by running a parent and child Pipeline on the same Snaplex node because data is not transferred over a network.

To set a dedicated Snaplex for a project, an Org admin can move a Snaplex from the Shared project to any other project. In Manager and Designer, only those Pipelines within the new project have access to that Snaplex. However, regardless of the Project containing the Snaplex, you can still run Pipelines on it as long as you have access.
The parameter runtime_path_id allows users to specify the Snaplex for OAuth2 operations in the Snap. This availability ensures that the refresh token is sent to the nodes in the given Snaplex.

The runtime_path_id enhancement is currently available for REST and API Suites Snap Packs.