How to setup recursive workflows in bubble.io

Поділитися
Вставка
  • Опубліковано 22 жов 2024

КОМЕНТАРІ • 12

  • @jwem18
    @jwem18 11 місяців тому

    Amazing, thanks for your help!

  • @kazi_goni
    @kazi_goni Рік тому

    This was really helpful. Thank you for this.

  • @AliPirani007
    @AliPirani007 6 місяців тому +1

    how would loops within loops work? So I have a list of tags, I want to update each tag with + 1 for every time the tag appears within a list of tags in the product.

    • @Michael-kp4bd
      @Michael-kp4bd 5 місяців тому

      That’s the type of thing I want to do, which is how I found myself here.
      I haven’t tested, but it seems this “recursive workflow” which acts as a loop, would allow for a nested recursive workflow (equivalent to a nested loop) - as you seem to understand by asking the question!
      There is another option “Schedule an API workflow on a list” to look into, but that might be a rabbit hole in the wrong direction. I think that might just be a shortcut to avoid having to set an exit condition - it would just run until the end of the list.
      I’d imagine your actual solution will use this single “API workflow” (But call it update-tags, because that’s what you’re trying to do) and the events will also use the normal “schedule API Workflow” - there will just be TWO of these events (after the first step, “make changes to a thing.. which I’ll get to)
      For this single workflow, do the same setup (2:05) but also include a parameter for Tag (also mark it as a list). ALSO add 2 more parameters: tag-index and tag-count.
      First step (event) would be to “make changes to a thing” and that thing would be a tag (more on that later)
      The THIRD step one would look almost exactly like the “schedule API workflow”, like shown at 5:50.
      But on this event, you’ll likely have to set the tag-index to 1. This represents getting through your tags on the single product, and calling the function again on the next product, starting with the first tag.
      Now going to the SECOND event, you’ll have to make ANOTHER “schedule API workflow” event, placed right before the THIRD event outlined above. In this one, you’ll instead be setting your tag-index to tag-index + 1, and condition is tag-index

  • @ezenon
    @ezenon 4 місяці тому

    yes actually very good solution and can be implemented various way!

  • @TechnischeDienstBoekestijn
    @TechnischeDienstBoekestijn 4 місяці тому

    Could I use a recursive workflow to copy records from one database into another one? Let's say I have a database with Events and because it has more than 10.000 records on it, I would like to creata a new database called Events2023 so then I could copy only the items from Events that occur in the year 2023. If this is possible, how to do it?

  • @raphb7653
    @raphb7653 10 місяців тому +1

    Curious why you wouldn't just use the "Schedule API workflow on a list" and select your list of products, this will loop all items every x seconds automatically, instead of creating basically a "manual loop" like in your video. Cheers!

  • @ReegunRufus
    @ReegunRufus Рік тому

    Hey, how and when should I use the "cancel the scheduled API Workflow" option kindly let me know!

    • @airdevco
      @airdevco  Рік тому

      Hi, please use cancel schedule API workflow option if you find yourself in an infinite loop. This can occur if you have an incorrect conditional and the recursive calls never end.
      To do so cancel this you can ---> Go to logs ---> Go to scheduler ---> Press show ----> Press cancel