Whilst this thread has been bumped, just wanted to say I never realised how useful this update would be. It’s amazing what a difference rapid workflows make. We went from 1 per second to about 50 per second. It should’ve been a new version as it broke many BE workflows that involve editing lists due to race conditions, but that aside, damn good job.
5 Likes
Thanks a lot, @boston85719 & @aj11, for detailing this helpful technique for detecting when a list’s last scheduled workflow is run (with the key caveat that the last to be scheduled is not necessarily the last to be run). I followed your exchange in April, and fortunately recalled it today when I needed to utilize the technique. I did have a difficult time finding your explanation again–consider posting a dedicated tip.
I agree database bulk action or list is like 150x slower than with any regular SQL database
Yes it is really fast but how did you solve the race condition problem? Did you switch everything on a list to recursion so that the API Workflow re-schedules itself?
No, I scheduled a 2 second interval where necessary which seems to be safe.
Small case here to share the improvment we see with this new release.
We have two related recurring process in backend WF that was taking around 24h to process before and according to WU chart logs, cost around 170 00 WU. This month, we moved to WU plan fo this app and was ready to test this new feature. Results: 2h30 to process the same quantity of data and 85% less WU used (25 000).
We are using an API and have a gap of 3 sec between calls for the first part of recurring WF to avoid rate limit on API provider. But the second part of the WF doesn’t have any inteval.
4 Likes
I can confirm “schedule api workflow on a list” is still buggy, some times it skips items from the list.
For example, when it is a list of texts and each text is different.
Setting 2 seconds interval didn’t work, 5 seconds seem to be working for now. However, it would be nice to be able to run parallel workflows reliably, for faster processing.
Hope this can be fixed soon.
2 Likes
Seeing as @steven.harrington was last active on the forum in August, @fede.bubble could you please take this up with the team?
Fastest/easiest way is to submit a bug report and the team will take a look. Go to the support page and tell the chat bot you want to submit a bug report. Thanks all!
1 Like