Running one-off cron jobs is necessary in many scenarios, such as triggering a one-time alarm, handling subsequent processing after an event, etc..
In standard implementations of cron, the year field is not included in cron expression. Without introducing new tool (such as "at" command), scheduling a one-off cron job could be troublesome and confusing under those circumstances.
The bother involves adding a cron job and waiting for it to be triggered, and then "remembering" to delete it manually on time before next year's execution. Some may use an automatic method to delete the cron job once it's executed, but deleting it automatically could create a false impression that the cron job was never added and executed.
To completely solve the problem, free our users from all those hassles they could encounter and let them can still utilize the power of cron expression, EasyCron added the year field to the cron expression. The implementation is clean, causing no confusion, and no additional action is required to take after cron job execution to achieve running cron job once.
Furthermore, after the cron job is executed, just as inspecting a regular cron job, you could check a one-time cron job's execution result on EasyCron at any time to troubleshoot possible issue.
We hope that the new capabilities that the "year" field brought help.
No comments:
Post a Comment