API Workflow - Multiple Users Triggering at Once

Hi,

I am pretty new to Bubble.io and this is a question I couldn’t find answered in other threads.

Instructors will be using my app to create PDF certificate’s for students. They may have 15 students, and I would like for them to be able to generate all 15 certificates with one button click. It seems like using an API workflow may be a good idea so that they not waiting on their own browser to complete the task.

Here’s my question, the bubble documentation says not to run the same API workflow more than once at a time. But what if more than one user is logged into the app and they select to generate certificates at the same time? They would not be accessing the same data, as no instructor will ever have the same student as another. So is that referring to not more than once with the same data or not more than once regardless of the data used? Or is it best to still just complete this with the standard workflow?

Sorry if this is a newbie question. Just haven’t been able to find the answer.

You’re correct

Where does it say that?

The more you have running at the same time, the more your app could slow down in the backend (obviously).

You’re overcomplicating it :slight_smile:

All you need to do is this:

  1. Create a backend workflow that takes Student (probably a User) and Course/Class as parameters. This workflow uses the Student and Course/Class data to generate a certificate and send it by email or whatever you want to do.
  2. Schedule API workflow on a list when instructor presses the generate certificate button. This will mean that each API workflow will receive different Students and Course/Class data and will create the PDF customised to each user.

So if you have 15 students, this will create 15 workflows (think of them like ‘tasks’) that Bubble will then begin processing as fast as it can.

Thanks for the reply and info! I’ll try and see where I read that. But it definitely caused me to have questions.

Good place to start

Awesome, thank you. Will definitely take a look at that.