Backend Operation Timing Out

I submitted a ticket to Bubble but haven’t gotten any response. My app ranks users based on their points each week. The workflow that does that searches for Members with 3 simple filters and then runs another workflow. Scheduling this workflow makes my app timeout repeatedly.

Currently there should be somewhere between 1500-2000 members returned in that result so it’s not crazy big. I can’t batch this operation because the index is what determines the ranking at the time this workflow is ran.

Any ideas on how to get this to run?

Sorry, but its not clear to me are you execution on a list, or one item a time in a list. some time executing on a list of item time out.

Sorry about that. It’s a list passed to a single workflow (not schedule on a list). This then “loops” through each individual item. The workflow itself is failing to start though.

ok i can see, you are scheduling the working on current time, which is making all the schedule workflow in less gap, like 1 ms, Try to add plus 2 second on scheduled date current date/time + 2 seconds

It will probably give enough time to each workflow to run.

Please check out the picture again. I am not using the “Schedule workflow on a list” action. I am scheduling a single workflow on a list that “loops” on that list. I can’t use schedule workflow on a list because I can’t pass an index into that.

Bro, i understand, you are runing a workflow which is scheduling it self, again and agian right, but the gap is very minute you have to add 2 second gap between each.

if you free we can take a look on it. i be able to understand you better.

That’s incorrect though. I am simply trying to start the loop off. This action is passing in the 1500 records that will then run record by record in the “loop” workflow. A gap isn’t relevant because nothing has even started in this case.

As you wish bro, i simpley wanted to assist you. :slight_smile:

but, for argument only if you give thet schedule few seconds and see if its working or not.

An other issue would be:

as you are scheduling it on current time, and the search is maybe the search taking time, and thats why its time outting.

i got some time so i thought maybe i could help you. but its your choise.

its look like the 3rd step is time outing, would it be possible if you can show the 3rd step, kindly.

What’s the schedule-cp-update action look like? Just scheduling for the next day? If so I would move Step 3 to the beginning so its scheduled right away without the other steps messing it up.

What’s the workflow look like in the weekly-jobseeker-summaries look like?

Is your app at/near max capacity around this time its being scheduled?

For reference, the weekly-jobseeker-summaries workflow was simple stuff like updating a thing and sending an email. App was nowhere near max capacity at any point in running the workflow.

My solution that I will test on Monday in live is sending the unique ids for each Member to the weekly-jobseeker-summaries workflow so it’s a lighter data load. Then in that workflow, I just make a change to the Member in the first action and reference “Result of Step 1’s Member” for the other actions in the workflow. Thanks for your help!

^^^ it’s always a good idea put the action that schedules the recurring workflow at the start when at all possible

I’m pretty sure it’d be the same - providing a list of data type is essentially providing a list of unique IDs to Bubble

This topic was automatically closed after 70 days. New replies are no longer allowed.