# Disable Workflow Timeout

**URL:** <https://forum.bubble.io/t/disable-workflow-timeout/53446>\
**Category:** Database\
**Created:** [April 2, 2019, 7:13pm UTC](https://forum.bubble.io/t/disable-workflow-timeout/53446 "2019-04-02T19:13:55Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![help](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/help/32/166707_2.png) [@help](https://forum.bubble.io/u/help)\
**Post date:** [April 2, 2019, 7:13pm UTC](https://forum.bubble.io/t/disable-workflow-timeout/53446/1 "2019-04-02T19:13:55Z")

</div>

Hi all, @neerja

I am building a Brand Mentions app that creates around 100 things per day, per user when we pull new data from an API.

Sometimes the workflow times out or says the app is busy try again later, is there a way to disable Workflow/schedule API workflow timeouts so it takes a long as It needs to process the data?

Reece

---

<div class="post-metadata">

**Author:** ![Kfawcett](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/kfawcett/32/38097_2.png) [@Kfawcett](https://forum.bubble.io/u/Kfawcett)\
**Post date:** [April 2, 2019, 7:25pm UTC](https://forum.bubble.io/t/disable-workflow-timeout/53446/2 "2019-04-02T19:25:18Z")

</div>

The “app to busy” probably means you need to add more capacity or slow down your API workflow. Bubble seems to kill all processing if you exceed the capacity – not the ideal way for them to handle it, but not too much we can do about it right now.

---

<div class="post-metadata">

**Author:** ![help](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/help/32/166707_2.png) [@help](https://forum.bubble.io/u/help)\
**Post date:** [April 2, 2019, 7:25pm UTC](https://forum.bubble.io/t/disable-workflow-timeout/53446/3 "2019-04-02T19:25:56Z")

</div>

Hmm, I had a feeling that would be the case for that, thanks.

Looks like I’ll need dedicated plan at scale.

---

<div class="post-metadata">

**Author:** ![nicolas\_dap](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/nicolas_dap/32/26345_2.png) [@nicolas\_dap](https://forum.bubble.io/u/nicolas_dap)\
**Post date:** [April 2, 2019, 7:55pm UTC](https://forum.bubble.io/t/disable-workflow-timeout/53446/4 "2019-04-02T19:55:47Z")

</div>

I agree. I often timout just me scheduling an API Endpoint on an important list of Things.

---

<div class="post-metadata">

**Author:** ![Kfawcett](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/kfawcett/32/38097_2.png) [@Kfawcett](https://forum.bubble.io/u/Kfawcett)\
**Post date:** [April 2, 2019, 7:58pm UTC](https://forum.bubble.io/t/disable-workflow-timeout/53446/5 "2019-04-02T19:58:13Z")

</div>

See if you can add more time between creating each API list item by upping the interval.

![image](https://us1.discourse-cdn.com/bubble/original/3X/d/d/dd2180cc1d88086b6a31629d6b009b48245799bd.png)

---

<div class="post-metadata">

**Author:** ![reger-alexander](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/reger-alexander/32/22827_2.png) [@reger-alexander](https://forum.bubble.io/u/reger-alexander)\
**Post date:** [April 2, 2019, 8:14pm UTC](https://forum.bubble.io/t/disable-workflow-timeout/53446/6 "2019-04-02T20:14:30Z")

</div>

Are you using api workflows on lists?

If yes, instead of scheduling api workflows on lists, try to schedule recursive single api workflows.

That way, they should run one by one without maxing out your capacity.

---

<div class="post-metadata">

**Author:** ![romanmg](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/romanmg/32/237672_2.png) [@romanmg](https://forum.bubble.io/u/romanmg)\
**Post date:** [April 2, 2019, 8:17pm UTC](https://forum.bubble.io/t/disable-workflow-timeout/53446/7 "2019-04-02T20:17:34Z")

</div>

Reece, try changing your workflow to a recursive system. If the amount of time it takes to process the full list reliably doesn’t matter as much, then this is the way to go. You’ll only need as much capacity necessary to process one item at a time since that’s how it would run.

> [@\[New Feature\] Scheduling API workflows can now be done recursively](http://forum.bubble.io/t/new-feature-scheduling-api-workflows-can-now-be-done-recursively/37372):
>
> Hi all, We had previously restricted scheduled API workflows from scheduling themselves (or scheduling another workflow that then scheduled itself). This restriction is now removed. Recursive scheduled workflows can be useful in situations where you are processing an unknown quantity of data that might be quite large. For instance, the following workflow will make sure every Thing in your database has been processed within 7 days: Processing data this way is generall…

@reger-alexander you beat me to it!

---

<div class="post-metadata">

**Author:** ![nicolas\_dap](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/nicolas_dap/32/26345_2.png) [@nicolas\_dap](https://forum.bubble.io/u/nicolas_dap)\
**Post date:** [April 2, 2019, 9:45pm UTC](https://forum.bubble.io/t/disable-workflow-timeout/53446/8 "2019-04-02T21:45:59Z")

</div>

It’s not about processing the workflows.  
I mean that the app timeout when the action “Schedule on a list” is triggered (when you see the upper progress bar)

---

<div class="post-metadata">

**Author:** ![help](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/help/32/166707_2.png) [@help](https://forum.bubble.io/u/help)\
**Post date:** [April 4, 2019, 9:23pm UTC](https://forum.bubble.io/t/disable-workflow-timeout/53446/9 "2019-04-04T21:23:25Z")

</div>

Awesome thanks a lot for that! I’ll give that a go!
