# Backend workflows slowing my app down

**URL:** <https://forum.bubble.io/t/backend-workflows-slowing-my-app-down/176725>\
**Category:** Database\
**Created:** [November 3, 2021, 9:12pm UTC](https://forum.bubble.io/t/backend-workflows-slowing-my-app-down/176725 "2021-11-03T21:12:36Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![beccijanereid](https://avatars.discourse-cdn.com/v4/letter/b/f0a364/32.png) [@beccijanereid](https://forum.bubble.io/u/beccijanereid)\
**Post date:** [November 3, 2021, 9:12pm UTC](https://forum.bubble.io/t/backend-workflows-slowing-my-app-down/176725/1 "2021-11-03T21:12:36Z")

</div>

Am I missing something here?

I thought moving actions to the backend workflows would speed up things for the user; however it seems my app is running even slower now I’ve scheduled things to happen in the backend…

I’ve read a bunch, followed all the guidelines I can find on how to speed up searches (moving as many constraints to the front etc. etc.)… and it seems it’s the simple move of moving from standard workflows to backend workflows which is making a big difference in slowing things down…

---

<div class="post-metadata">

**Author:** ![ed727](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/ed727/32/71942_2.png) [@ed727](https://forum.bubble.io/u/ed727)\
**Post date:** [November 3, 2021, 10:31pm UTC](https://forum.bubble.io/t/backend-workflows-slowing-my-app-down/176725/2 "2021-11-03T22:31:56Z")

</div>

Depends on the nature of the workflow. While a backend workflow takes the process out of the front end, it does take time/resource for the front end to schedule the backend workflow. Workflows that are relatively simple and need to be done immediately are usually best kept on the frontend. Workflows that take longer periods of time and aren’t immediately needed generally are best for the back end. As in many things in life, the answer is “it depends”.

---

<div class="post-metadata">

**Author:** ![beccijanereid](https://avatars.discourse-cdn.com/v4/letter/b/f0a364/32.png) [@beccijanereid](https://forum.bubble.io/u/beccijanereid)\
**Post date:** [November 8, 2021, 8:12pm UTC](https://forum.bubble.io/t/backend-workflows-slowing-my-app-down/176725/3 "2021-11-08T20:12:05Z")

</div>

For the items that need immediate attention, I’ve tried using backend workflows for actions happening multiple times on multiple pages - but perhaps I need to be more creative with using custom events in repeatable elements instead. Thanks!

---

<div class="post-metadata">

**Author:** ![ed727](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/ed727/32/71942_2.png) [@ed727](https://forum.bubble.io/u/ed727)\
**Post date:** [November 8, 2021, 8:50pm UTC](https://forum.bubble.io/t/backend-workflows-slowing-my-app-down/176725/4 "2021-11-08T20:50:41Z")

</div>

Nice overview of reusables in the below post in case you hadn’t seen it. However I don’t think they speed up app performance on their own – only if they happen to reduce the number of elements/workflows on a page. Could be wrong though.

> [@A guide to advanced use of reusables](http://forum.bubble.io/t/a-guide-to-advanced-use-of-reusables/63884):
>
> A recent thread about the Bubble editor becoming sluggish over time spawned another discussion: reusable elements can speed up the editing of complex pages significantly, but as it was rightly pointed out, they can also make the editing of an app a lot more complicated. Having worked on some very large one-page apps, I’ve become a reusable group proponent by necessity. It’s a fact of life at the current stage Bubble is in, that as the number of elements and workflows increases, the editor become…