Replies: 1 comment
-
|
I am realizing now that the limitations on children and grandchildren is just for the fluent api. Still curious on not allowing children of CRON entities. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I am implementing a scheduler into a system. I am carefully weighing my options and am interested in giving TickerQ a shot. I have read through all of the documentation and am curious...
Why is job chaining not supported for CRON jobs? Is there an underlying design limitation causing this decision? What if I need to trigger a job once a day that will trigger many children in order with different branches depending on the outcome and/or status?
Also, why is there a limit on the amount of children and nested children? What's happening under the hood that prevents this from being extended upon?
Surely I can just queue jobs at the end of jobs right? Wouldn't this be the same thing but without the nice readability and transparency of orchestrating everything in one place?
Beta Was this translation helpful? Give feedback.
All reactions