I found a way to run API Workflows sequentially

betteredbritain · 2024-11-18T06:44:15.616Z

Not sure if its just me but this post we are all responding looks ai generated, so I would take it with a pinch of salt. WU on this flow would be off the charts and the flow would take at least a couple of minutes to complete depending of course on the number of items on the list.

antolin.lacaton · 2024-11-18T09:14:41.690Z

boston85719:

This method costs way too much WUs, is too cumbersome to setup and maintain. Would be better to use custom events and bulk updates via API connector. I highly recommend asking ChatGPT to give you a better approach than this one it gave you.

You’re not the first to tell me, but I haven’t managed to do what I wanted with custom eventts. Do you have any concrete use cases for multi-step logic that work for you?

antolin.lacaton · 2024-11-18T09:18:12.301Z

betteredbritain:

Not sure if its just me but this post we are all responding looks ai generated, so I would take it with a pinch of salt. WU on this flow would be off the charts and the flow would take at least a couple of minutes to complete depending of course on the number of items on the list.

hahaha it’s true that I used GPT to clean up the method so that it could be understood by as many people as possible, since I find it quite complex to explain!

In terms of WU, I don’t see much difference compared to my old system where I used to play with the “Current date time +second” before launching the next step, but I was convinced that it was more reliable in the long term.

Do you have any other ideas for achieving the same result without consuming too much WU?

antolin.lacaton · 2024-11-18T09:26:54.521Z

I don’t know if it makes any difference, but my system has to work entirely on the backend so that my user doesn’t have to be logged in for the logic to be triggered!

antolin.lacaton · 2024-11-18T09:30:10.904Z

I don’t know if it makes any difference, but my system has to work entirely on the backend so that my user doesn’t have to be logged in for the logic to be triggered!

That’s one of the problems I had with custom events, I couldn’t store the results in a custom state since the user isn’t logged in.
What’s more, the next step takes into account the entire list from the previous step before launching.

Example: If I update a recipe’s ingredient list, I need to take all the updated ingredients to update the recipe (to add up all the costs and define the new margin).

I’m sure this isn’t the most efficient way, but if you’ve got something better, I’d love to know it!!

georgecollier · 2024-11-18T09:49:34.387Z

antolin.lacaton:

Example: If I update a recipe’s ingredient list, I need to take all the updated ingredients to update the recipe (to add up all the costs and define the new margin).

So just have a trigger when an ingredient is changed, ane Make changes to the Recipe with Do a search for Ingredients:each item’s cost:sum.

Don’t overengineer it!

antolin.lacaton · 2024-11-18T09:57:17.421Z

georgecollier:

So just have a trigger when an ingredient is changed, ane Make changes to the Recipe with Do a search for Ingredients:each item’s cost:sum.

Don’t overengineer it!

I’ve already tried to make it simpler, but bubble goes too fast and some results are overwritten by other operations, making the whole thing unreliable!

My software allows you to follow the evolution of cost variations over time, so each ingredient contains a list of “ingredient history” with a price associated with a date. The same applies to recipes.

An imported invoice can modify 15 ingredients in a single recipe just as it can modify only one (or 0 in some case), and I find it odd to update the recipe 15 times (for each ingredient)… What’s more, the recipe itself can become an ingredient in another recipe, so the complexity multiplies with each step…

As someone with a lot of experience, have you ever seen software like this? That are a little complex in their logic? Your opinion could help me a lot!

georgecollier · 2024-11-18T09:59:16.117Z

antolin.lacaton:

some results are overwritten by other operations, making the whole thing unreliable!

That’s race conditions, as a result of using a List on a data type. Just use a search.

antolin.lacaton:

As someone with a lot of experience, have you ever seen software like this? That are a little complex in their logic?

Yes, and overengineering something like this tends to cause more problems than it solved.

antolin.lacaton · 2024-11-18T10:01:02.224Z

georgecollier:

That’s race conditions, as a result of using a List on a data type. Just use a search.

So according to you, for each step I should just set a trigger that detects a change, and once done I automatically launch the next step?

And how do I know that the previous step is finished and that I can launch the next one?

code-escapee · 2024-11-18T13:41:04.256Z

By putting the next step in a seperate custom event…

antolin.lacaton · 2024-11-18T14:36:31.447Z

Do you have a simple, concrete example so that I can better understand what you’re trying to tell me?

georgecollier · 2024-11-18T18:28:53.843Z

Step 2 will always run after Step 1

CleanShot 2024-11-18 at 18.28.26@2x1560×510 22 KB

jagdish_bajaj · 2024-11-18T20:32:53.754Z

@antolin.lacaton I don’t think this level of complexity is warranted for the use case you describe.

A combination of database triggers and BEWF supported with custom events should suffice. In addition, instead of updating data instantly, I would recommend using recurring events to run daily or weekly routines to loop over data that is not time-critical.

antolin.lacaton · 2024-11-19T11:21:08.486Z

georgecollier:

Step 2 will always run after Step 1

CleanShot 2024-11-18 at 18.28.26@2x1560×510 22 KB

And when I have to wait for a list of items to be modified/created, what do I do?

antolin.lacaton · 2024-11-19T11:24:48.969Z

jagdish_bajaj:

@antolin.lacaton I don’t think this level of complexity is warranted for the use case you describe.

A combination of database triggers and BEWF supported with custom events should suffice. In addition, instead of updating data instantly, I would recommend using recurring events to run daily or weekly routines to loop over data that is not time-critical.

The first version of my method wasn’t as complex, but I had a lot of data that was overwritten due to the fact that bubble was going too fast and triggering steps in parallel!

Recurring events wouldn’t be efficient enough, because that’s precisely my value proposition for this software: to analyze data quickly and reliably for my users.

If you can think of any other way I could avoid such a complex process, I’d love to hear from you!

boston85719 · 2024-11-19T11:45:48.272Z

In the example from @georgecollier it is not always true that step 2 will always run after step 1…what is true based on the screen shot used in the example, is that step 2 will always trigger after step 1 has been triggered, but nothing in that example screen shot demonstrates how to actually ensure that step 2 will always run after step 1…in order to do that, step 2 needs to take a value from step 1 using ‘result of step 1’, which can be the new version

Custom triggers will make it so that all actions in that custom trigger will complete before other actions from the original series get triggered. For example, original series is step 1, step 2 (trigger custom), step 3 and the custom trigger has 5 steps…all 5 steps in the custom trigger will complete before step 3 from the original series is triggered.

Also, when using result of previous step in a subsequent step as a data source or condition, will cause the subsequent steps to ‘know’ the result of previous step even if that previous step has not competed, so Bubble smartly maps the correct values.

Also, if you want to avoid race conditions, you can use the app API to do bulk create things, take the result of that API call which is the list of unique IDs of all data entries created via that API call and then run the action to update the data field of the other data type, that data field being the list of related things…at least that is the most optimal way to do it, but you’ll find a lot of discussions on the forum for other ways to achieve similar results in terms of avoiding race conditions.

georgecollier · 2024-11-19T11:49:47.976Z

boston85719:

it is not always true that step 2 will always run after step 1

Referencing Bubble manual:

In a workflow with two actions, if Step 2 is using a condition based on a search depending on data manipulated in Step 1, then Step 1 should be implemented into a custom event to make sure it is finished before moving on to Step 2.

If a backend workflow should be triggered after other steps in the workflow, then it should be implemented in a custom event placed after the steps that need to come first.

Custom events will always run in sequence, and any steps in a main workflow before a custom event will run before the custom event itself is triggered.

boston85719 · 2024-11-19T12:06:12.485Z

georgecollier:

any steps in a main workflow before a custom event will run before the custom event itself is triggered.

That is new to me. I wonder if it has always been that way, or a newish improvement. Thanks for sharing.

antolin.lacaton · 2024-11-19T12:08:55.588Z

georgecollier:

Custom events will always run in sequence, and any steps in a main workflow before a custom event will run before the custom event itself is triggered.

So it would also be possible to manage variable data lists?

There are a lot of steps where I have to wait for a data set to finish being modified/created before launching the next one.

For example, to update my recipe, I’ll wait until all the ingredients have finished updating. Similarly, to update my average margins, I’ll have to wait until all my recipes have been updated before doing so!

antolin.lacaton · 2024-11-19T12:12:51.805Z

To give a concrete example:

I launch an API Workflow on an ingredient list.
This API will take the list of my ingredients and update them all.
I then have to take the whole list, find the associated recipes and update a new recipe list (so I’m also working via a Workflow API on a list).

And this logic runs several times to update all the data I need: the result of one list allows me to update the next etc…