Thanks for the response Jack.Apologies, I could have been a little more specific. My question was in relation to SFTP transmission protocol.
I understand that the CD protocol may have a built-in feature to attempt connection to an alternate endpoint if the definition for the Snode has any "Alternate Comm Info".... but I don't believe there is any such ability or configuration for SFTP.
So I'm wondering how best to configure SFG to handle a failure to an SFTP endpoint. For example if your partner has two SFTP servers to allow for resiliency, and there is no load balancer or other device to handle the failover at the network level, and so you configure a single SSH remote profile for the primary server of your partner. If that server is down, is there any way to automatically divert a different SSH profile for the secondary server / or otherwise override the configured destination ?
Using a custom delivery protocol would allow you to build a delivery BP that can do anything you wish. And as part of that protocol, you could collect the primary and alternate delivery channel configuration the process would use, if needed.Example: