Ahh I see. Well, without a load balancer the On-premise URL is dependent on having an actively connected ground node.
So, If the node the task is configured for is coming down and going back up a lot, or is changing often, then the cloud URL might be more so of what you are looking for. The cloud URL is not tied to a particular node. So, if there are available nodes in the plex that this job is configured to run on then the cloud URL will schedule it there. However, the caveat here is that data in and out of the pipeline will go through our servers, whereas a ground trigger avoids that.
Can you elaborate on the data in and data out ? You mean to say the input parameter value and out put of the triggered pipeline ?
Much thanks for your feedback. I’m still testing but it’s now working as expected as far as I can see.
Questions on using the SQL Server – Merge snap, where is WHEN MATCHED logic? | SnapLogic - Integration Nation - 6636
