08-27-2024 09:30 AM
We are experiencing an issue when invoking the triggered task using the Groundplex URL. The problem is that when we trigger the task using the Groundplex URL (load balancer URL), it immediately returns a 200 response code. It does not wait for the job to complete before returning a success status. I am wondering why the 200 response code is returned immediately upon triggering instead of waiting for the job to complete. The triggered task cloud URL behaves as expected; we only encounter this issue with the Groundplex URL. Any help would be much appreciated.
Solved! Go to Solution.
08-28-2024 01:09 PM - edited 08-28-2024 01:09 PM
Check the pipeline on your Trigger Task for closed output view(s). Cloud URL (elastic.snaplogic.com) are synchronous (with or without open output view) but Groundplex URL are asynchronous with pipelines having closed output view(s). Having an open output view in the pipeline allows the Trigger Task on the Groundplex URL to become synchronous.
08-28-2024 01:09 PM - edited 08-28-2024 01:09 PM
Check the pipeline on your Trigger Task for closed output view(s). Cloud URL (elastic.snaplogic.com) are synchronous (with or without open output view) but Groundplex URL are asynchronous with pipelines having closed output view(s). Having an open output view in the pipeline allows the Trigger Task on the Groundplex URL to become synchronous.
08-29-2024 11:37 AM
Thanks for the suggestion @acbradley, it worked !