...

Two additional configurable URLs (Secure Alternative URL and Unsecured Alternative URL) appear on the Task Details page. Unlike the Snaplex URL, which always runs on the Snaplex defined in the Task, you are responsible for defining a High Availability architecture, and it is commonly done using a load balancer or the network's DNS. The Alternative Snaplex URL was introduced for users interested in setting up their Tasks to run in High Availability configurations.

...

You can also determine if Snaplex nodes are not communicating by clicking Dashboard > Health, selecting the Snaplex, and viewing the Alerts for each node. If communication issues exist, an alert such as Neighbor connectivity alert might appear.

Configure Triggered Tasks for High Availability with

...

Snaplex URLs

The Alternative Snaplex URL triggers a Pipeline to run on any Snaplex, regardless of what is defined in the Task. The Alternative Snaplex URLs differ from the Snaplex Alternative URLs because you can use them to trigger a Task to run on any Snaplex node, whereas the Snaplex URL always runs on the Snaplex node that was specified when the Task was created.

A Triggered Task assigned to Snaplex A always runs on that Snaplex when triggered with the Snaplex URL. Therefore, even if triggered on a node on Snaplex B, the Task still runs on Snaplex A. However, if you use the Alternative Snaplex URL, then the Task runs on Snaplex A when triggered on Snaplex A and Snaplex B when triggered on Snaplex B.

For example, if a Task is configured to run on Snaplex A, then you can force it to run on Snaplex B by substituting the host name and port of a JCC node or FeedMaster in Snaplex B, in place of the one configured in the Alternative Snaplex URL. 

On the same screen, you can review the Task status to determine if you need to run a Triggered Task on another Snaplex. Furthermore, clicking on the Task detail displays a window with Pipeline statistics, parameters, and information such as path, node, and the user who ran the Pipeline.

...