New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provide once trigger #89
Comments
related to #86. |
could you elaborate: what are the ("lot of") problems with layering this on top of cron? I would hope the cron implementation can handle this pattern without difficulty. |
i think carlos wants it to auto-destruct after firing. if done via rules, there is a race. it could be done with a sequence wrapper around the activated action, i suppose. |
Under the hood we the implementation will use 'new Cron(new Date(stringdate))' The a lot problems was more on capturing the users point of view. To some users it would be confusing trying to understand that we can "hack" cron to take a date string. Also provides a cleaner API to ask the user what it wants to do with the trigger when done. This is a building block for when we get to a point of the feed service create a rule for them and have a syntax like |
👍 on this feature and an optional parameter to "delete after firing". I can see lots of use-cases when an action wants to schedule a trigger to fire a set period after it is running using this approach. |
👍 this would be a very useful feature for me as currently I'm having to run clean up jobs looking for stale triggers and rules. For my perspective it would be good to have an uber trigger that encapsulates the trigger and rule e.g. a It's the job which I can designate as |
The first phase of trigger once is done. I opened a new issues #123 to discuss the deletion of the trigger and rules after fire. Closing for now |
Feature request:
A user would like for a trigger to be fire once at a specific time and date, and optionally delete the trigger after the fire.
One idea for UX could be: (at is UTC based)
current stat is to set a cron trigger with maxTrigger of 1, which would cause a lot of problems in terms of cleaning up "dead" triggers and trying to guesstimate when is going to actual fire.
The text was updated successfully, but these errors were encountered: