# Recurring workflows

If you need to run a workflow multiple times with a set interval in-between, you an use a *Do every 5 seconds* event.

<figure><img src="https://34394582-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M5sbzwG7CljeZdkntrL%2Fuploads%2FhL8r6FrJl8noJRZiNgHS%2Fdo-every-5-seconds-bubble.png?alt=media&#x26;token=16c89450-2355-4c5c-b730-22a7581ecd78" alt=""><figcaption></figcaption></figure>

The **5** is flexible, so you can set it to any number of seconds that you want, including decimals, and the workflow will keep running until you stop or the page is closed.

<figure><img src="https://34394582-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M5sbzwG7CljeZdkntrL%2Fuploads%2FmGwrQxwrTB9X9Bu5GNsg%2Fdo-every-flexible-seconds.png?alt=media&#x26;token=279edbb9-11cd-49e3-b4b5-3ed50c4597ad" alt=""><figcaption><p>The interval is customizable – in the example above, we've set it to 3.5 seconds.</p></figcaption></figure>

{% hint style="warning" %}
Keep in mind that continuously repeating a a workflow can potentially slow down your app (depending on what the workflow is doing), especially as your app scales with more users.

We recommend that you mostly use this event for [client-side actions](#user-content-fn-1)[^1], and that you do careful testing to see how it affects your app performance-wise if you are using [server-side actions](#user-content-fn-2)[^2] like database operations.
{% endhint %}

If you want to run a workflow continuously even if the page is closed, you may consider using [recursive API workflows](#user-content-fn-3)[^3] instead. Note that they can only run server-side actions.

[^1]: *Client-side actions* are actions that take place on the user's device (such as setting a custom state or changing the visibility of an element), as opposed to actions that happen on the server (such as database operations).&#x20;

    In the context of recurring workflows, client-side actions are more lightweight to process, since they require no data to be sent to and/or from the server.

[^2]: *Server-side actions* are actions that take place on the Bubble server, as opposed to on the user's device. Server-side actions include making changes to the database.

    In the context of recurring workflows, server-side workflows can be taxing on the Bubble server, since they involve sending information back and forth and spending server capacity.&#x20;

[^3]: Recursive API Workflows are backend workflows that run, and then schedule themselves to run one more time immediately or after a delay. They are useful for setting up workflows that should be repeated or executed on a list of things.

    Article: [Recursive API Workflows](https://manual.bubble.io/help-guides/integrations/api/the-bubble-api/the-workflow-api/api-workflows/recursive-api-workflows)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://manual.bubble.io/help-guides/logic/workflows/events/frontend-events/recurring-workflows.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.