...
The Alternative URL triggers a Pipeline to run on any Snaplex, regardless of what is defined in the Task. The Alternative URLs differ from the Snaplex URLs in that 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 if 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 URL is used, then the Task runs on Snaplex A if when triggered on Snaplex A and Snaplex B if when triggered on Snaplex B.
For example, if a Task is configured to run on Snaplex A, then you can force it can be forced 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 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.
...