kmiesse
Contributor
Joined 9 years ago
User Profile
User Widgets
Contributions
Re: CURL call for a triggered task dying after 15 minutes
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?1.2KViews0likes1CommentRe: CURL call for a triggered task dying after 15 minutes
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.2.7KViews0likes6CommentsRe: Dynamic DB Account Use Cases
Make sure you name the pipeline parameters without the leading underscore but when you refer to them in the child pipeline or account settings use the leading underscore. Make sure you can do this without the parent/child to eliminate any issues passing from parent to child. Just try it with one pipeline containing the snap set to the dynamic account.2KViews0likes0CommentsRe: Dynamic DB Account Use Cases
I just have the MySQL snap set to your-account-name dynamic MySQL account and the pipeline that has the MySQL snap has the pipeline parameters YourHostName and YourDBName. I also do pass these parameters from a parent pipeline to a child pipeline where the child contains the MySQL snap with the dynamic SQL account.2KViews0likes0Comments