Replies: 1 comment
-
|
Hey @mainrs,
This way the task/schedule system doesn’t limit you and can reuse the same logic across different execution paths. |
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 have the need for periodic tasks in my app. However, the data sources are API servers and provide caching hints for when to poll next time. Usually a timestamp.
The current system for scheduling tasks seems to only allow for two trigger scenarios:
Is there a way to trigger tasks from within loco by code? For example, the app would once create one-shot periodic tasks at startup and store their timers. And the tasks would re-schedule themselves once called.
It seems that the current task / schedule system is not meant for this type of work. :(
Thank you!
Beta Was this translation helpful? Give feedback.
All reactions