This topic was automatically generated from Slack. You can find the original thread here.
I have a workflow that is taking longer than the maximum 12-minute timeout. Is there a way to make this longer?
Based on the information provided in the Pipedream documentation, workflows have a default execution limit that varies with the trigger type, and this limit can be increased up to a maximum value set by your plan. For paid tiers, the maximum time per execution is 750 seconds (12.5 minutes). Unfortunately, if your workflow is taking longer than this maximum 12-minute timeout, there isn’t a way to extend this limit further within Pipedream’s current constraints. To address workflows that exceed this limit, you might consider the following approaches: 1. Optimize Your Workflow: Review your workflow to identify any inefficiencies or bottlenecks. Sometimes, optimizing the code or the logic can significantly reduce execution time. This might involve optimizing API calls, processing data more efficiently, or removing unnecessary steps. 2. Split Your Workflow: If possible, split your workflow into multiple parts. You can trigger a second workflow from the first one using Pipedream’s built-in actions or by sending an HTTP request to the second workflow’s endpoint. This approach allows you to distribute the workload across multiple executions. 3. External Processing: For tasks that require extensive processing time, consider offloading that work to an external system. You can trigger an external process and then poll for its completion or wait for a webhook that signals the process is done. For further assistance or to discuss your specific use case, you might find additional support by reaching out to Pipedream’s support team. Visit Support - Pipedream for more support options.
Great suggestions from Pi here! 
Webhooks are awesome. 