HTTP Communicate Node with Branching Paths
Posted: Tue May 26, 2020 7:34 pm
Hi All,
I'm trying to build a workflow that ends with a single success notice sent out via an HTTP Communicate node after a branching workflow has created two proxy files from the original. It looks like this:
The hold is set to Synchronize, however once both flows have reached the node to proceed, they both call the HTTP Communicate step, so I get two notifications.
I created an alternative workflow where one branch ends and the Hold is set to wait for both output files to exist, seen here:
This solves the multiple notification problem, but I'd prefer to run it as a Sync rather than a Check for various reasons.
Is there a way to merge the branches back into one for a Hold set to Sync that will generate a single notification?
Thanks!
I'm trying to build a workflow that ends with a single success notice sent out via an HTTP Communicate node after a branching workflow has created two proxy files from the original. It looks like this:
The hold is set to Synchronize, however once both flows have reached the node to proceed, they both call the HTTP Communicate step, so I get two notifications.
I created an alternative workflow where one branch ends and the Hold is set to wait for both output files to exist, seen here:
This solves the multiple notification problem, but I'd prefer to run it as a Sync rather than a Check for various reasons.
Is there a way to merge the branches back into one for a Hold set to Sync that will generate a single notification?
Thanks!