Does the schedule happen after the step to create a thing?
As a diagnostic, how about at the start of the workflow, write the parameters to a database thing, for a log record.
Does the schedule happen after the step to create a thing?
As a diagnostic, how about at the start of the workflow, write the parameters to a database thing, for a log record.
Just wanted to chime in with my two cents. I tried to replicate the example but it didnât work for me. I could see that the workflows were being scheduled recursively because the ID in the scheduler kept incrementing. However, the things werenât changing.
I had it set to âfirst itemâ so I tried setting it to ârandom itemâ and now itâs changing a thing every time the workflow runs.
Curious if anyone has thoughts on why it worked one way and not the other.
Recursive workflows work just fine. They are just artificially limited to be âslow AFââŚitâs not what weâre used to, either as casual Internet consumers or as developers. We are used to free = infinite. It is what it is.
@josh, are there any events that could stop a the scheduling of a recursive API workflow? I have a feeling that pushing a new version to live breaks it. I will need to test this again, because my logs donât go back far enough to check when the recursive scheduling stopped.
edit: i just checked that this is not the case. So something else makes my indefinitely scheduled api workflow stop. tbcâŚ
The information is really helpfulâŚthanks a ton.
@Bubble does this really continue indefinitely or is there something that would cause it to stop? I was running it to delete ~50k records, but it stopped with ~16k left.
where is the âwhileâ condition located? Wonât the âonly whenâ condition make it run a single time?
The âwhileâ is the action at the end of the flow that reschedules itself.
Anyone get more info on what stops an api fully completing?
When i have a recursive api running or an api running against a list, and it unexpectedly stops, in my case it stops at the time of a user doing something unrelated on the site which triggers a single api to complete a task.
Even though the userâs api is fast and a small task, it seems to interrupt any recursive api or list api tasks already running which then donât complete afterwards.
A little frustrating!
A quick question if I may - I am trying to process some 3k records and it runs through some 100 - 200 records and grinds to a halt. Not because of âwhileâ condition fails. Whatâs the best way to debug this?
Even if the task wonât time out, it can still be interrupted if you blow out all your capacity. I canât say for sure whatâs going on under the hood, but Bubble seems to have a tolerance for pushing the capacity for some time, before it gets unpredictable and may not finish.
Have you tried spacing them out more, by adding a couple of seconds between each process?
Hmm, ok, in most cases the should be fine, although itâs hard to say without knowing what your workflow is doing.
Sorry if Iâm pointing out obvious things here, but some more suggestions are:
If you donât mind sharing how the workflow was set up (including how it schedules itself), maybe we can spot something.
Actually it began to behave as expected on a repeat try (without any alterations) and completed the process. So I guess this was a platform issue rather than me. Hope Bubble logs will flag up issues!
I confirm the process may stop without any reason with recursive API workflows. Check the logs, you may find some âWorkflow errosâ
This can happen when the app gets too busy
Yep, another workflow randomly stopped. No error logs. Just stops. @josh , any thoughts on this. Looks like others like @nicolas_dap also experience the same issue of recursive workflows failing randomly. The app was not busy at the time in any way and server capacity has not maxed out.
It would be nice to have a bubble answer to this
So letâs say I want to send daily email reminders of pending task, I will have to start/send the first email batch and then the following emails will be automatically scheduled with no manual intervention? And what about the workflow limit on personal plans?
Yes. But you need to be considering the âlimitâ, so just donât try to send 1000âs of emails (i.e. run too many workflows)⌠be reasonable
well that is really freakn awesome ⌠yes yes and YES!