Forum Discussion

wani-amol's avatar
wani-amol
New Contributor III
7 years ago

CURL call for a triggered task dying after 15 minutes

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 con...
kmiesse's avatar
kmiesse
Contributor
6 years ago

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's avatar
RogerSramkoski
Employee
6 years ago

Hi Kim,

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

Thanks,
Roger

  • kmiesse's avatar
    kmiesse
    Contributor
    6 years ago

    I’m able to get executions longer that 15 min to run with the On-prem URL but I end up getting 504 Gateway Time-outs not even 5 or 10 minutes into execution when triggering the task with either the Execute button in Manager or with a curl. The pipeline finishes successfully. Do you have any insight into that, @rsramkoski?

    • kmiesse's avatar
      kmiesse
      Contributor
      6 years ago

      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.

    • dmiller's avatar
      dmiller
      Former Employee
      6 years ago

      I’ve forwarded this on to our Doc team.