Struggling with Recurring Workflow Data Retrieval – Any Tips?

Need help Database
1

Hello,

I need some assistance with my recurring workflow setup in Bubble. Here is the breakdown:

  • Task 1: Schedule API workflow on a list (creating Daily_user_balance)
  • Task 2: Schedule API workflow on a list (creating Daily_UV)

Tasks 1 and 2 work perfectly!

image
image1025×275 23.4 KB

  • Task 3: Custom Event (Trigger Daily_record)
    image
    image

  • Task 4 (Daily_record): Scheduled 10 minutes after Task 3, this creates the Daily_record thing.

I delay Task 4 to ensure I can ‘do a search for’ and retrieve the recently created items (Daily_user_balance, Daily_UV).
image

image

However, after several tests, I find that I can’t retrieve any list of Daily_user_balance or Daily_UV inside the Daily_record created.

I need help to understand what I might be setting up incorrectly!

2

@georgecollier , @adamhholmes, @MattN any idea ?

3

By debugging and looking more closely at the logs, I discovered that the problem is with the timing of the workflows’ execution. The ‘Do search for’ action to retrieve the data created in Task 1 & 2 is running before those tasks have finished.

Any idea how to delay the task 3 ?

I did read some posts very useful like ( [Feature Enhancement] Schedule 100k Workflows with Schedule API Workflow on a List - Announcements / New features - Bubble Forum) but still need help !

4

In the search constraints put the result of step 1 and result of step 2

5

I tried to used “result of step X” but look like it doesn’t work with Schedule API workflow on a list or I might be missing something. I’m having a problem to use the options/tags (available) of the “result of step X” to pass the data to my custom event or in the search constraint.

Do you have some examples?

6

This thread is very similar to your use case. Complete API Workflow before scheduling another API Workflow
There are multiple solutions that you can look at.

7

I see this more clearly now…you are trying to schedule a backend workflow in step 1, then another backend workflow in step 2 and the 3rd action is a custom workflow in the backend, and that 3rd action requires the results of the backend workflow from step 1 and backend workflow from step 2.

You need to run backend workflow 1, and after that has completed, which if it is on a list, when the last list item is done, for that backend workflow to schedule the 2nd backend workflow and when that backend workflow is done, schedule your custom trigger. It is a chain of backend workflows where once backend workflow 1 is done it schedules number 2 and when number 2 is done it schedules number 3.

1 Like
8

@animisha45 Thanks! Your advice was very helpful. I just discovered that all backend workflows run simultaneously. I’ve been using Bubble for over a year and was unaware of the order of operations. Now, I need to review hundreds of workflows :exploding_head:. Fortunately, I believe I have mostly followed these rules without knowing it.

Reading Order of Operation - #2 by aschofer and watching the video on Understanding Workflow Execution Rules gave me the solution.

Solution:

  1. Step 1: Trigger a backend custom event that runs workflows 1 and 2 (All workflows in a custom event are executed before moving to the next step).
  2. Step 2: Schedule an API Workflow to create a thing.
  3. Step 3: Make changes to the thing (using the result of step X)
9

I’m encountering an issue with custom events. One of my workflows does not seem to recognize the parameters for the constraints. Fortunately, the privacy rules work !

The log error
image

Schedule API on a list
image

image