At present, Flowable’s async task scheduling relies on the table ACT_RU_JOB to complete.
I would like to ask whether Flowable has considered using message queues to complete the scheduling ?
What are the risks of async task scheduling that does not depend on database ?
Hi, I’m also looking at the async executor docs. We don’t currently have any issues with it with our current volume, but just trying to understand how it works. Have you looked at Advanced · Flowable Open Source Documentation ? It doesn’t look like an out-of-the-box solution but it’s a start