CURL call for a triggered task dying after 15 minutes

Question

All,
We are trying to run a triggered task through a CURL call and the pipeline runs for more than 15 minutes. The CURL call dies after 15 minutes.
We found that the Cloud URL has a 15 minute connection limit whether a connection is idle or not. Is there a way around this or to maximise the connection limit?
We have a few options including batching up data in order to run the pipeline in less that 15 minutes but was wondering if we could maximise the connection limit somehow?
Any help is really appreciated. Thanks!
-Amol

dmiller · Answer

I’ve forwarded this on to our Doc team.

kmiesse · Answer

SOLVED: It was our load balancer having an idle timeout of only 5 minutes that caused the 504. We extended it and did not receive a 504 when trying the On-premises Secure URL.

tlui · Answer

Hello Amol,
Unfortunately, that is the platform limit that we have and enforce for connections. If you want a bit more detail and check on other timeouts that are enforced, please see https://docs-snaplogic.atlassian.net/wiki/spaces/SD/pages/1438691/Timeouts
Regards,
-Tim

kmiesse · Answer

Is this 15 minute limit on the On-premises Secure URL also?
We use pipelines to deploy pipelines (something we built before project migration was a feature and its worked well) but now its taking more than 15 minutes so we are unable to push changes.

rogersramkoski · Answer

Hi Kim,
No, the 15 minute limit does not exist for on-premise URLs. It is only the Cloud URL.
Thanks,
Roger

Forum Discussion

CURL call for a triggered task dying after 15 minutes

8 Replies

Recent Discussions

List column names from excel files

No output preview using a specific groundplex

Hi, Is there a way where we can add delay/wait of 3~5 seconds before every post call?

Automating Untracked assets to GIT

Pagination and nextCursor in header