Triggered Task node not available

[Ksivagurunathan]

Hello , Our snaplogic nodes are not load balanced currently. Snaplogic tied all of our production triggered task to one node. even though we have more than one node in production. If that nodes goes down or decommissioned for some reason, could we continue to use the task with cloud url instead of on-premises secure url ? Any faced the issue and what is the recommended solution here. Load balancing the nodes is not our first preferred option for short term solution.

[cjhoward18]

The input data will be sent to the control plane to then be sent to the node for execution, then the output of the triggered pipeline will be sent back to the control plane to be returned to the caller.

[Ksivagurunathan]

when the pipeline execution happens on different node other than the one tied in triggered task on-premise url, the same behavior like mentioned above would occur right ?

[cjhoward18]

Is this scenario a cloud triggered execution?

[tlikarish]

If the pipe is started by a ground trigger on-premise url and the pipe executes on a separate node, then the nodes will transfer data between themselves without going through the control plane. This keeps all data on premise and will likely perform better.