Closed guhkun13 closed 9 months ago
[SOLVED] Turns out this is because the effect of wrong sync [issue closed on https://github.com/robfig/cron/issues/514] . It looks like the cron did not updated, but in actuality, it updated. So i will close this issue.
Hi again, I found an issue when I remove the entry from the cron, the next hit will still hit the same entry ID that should have been removed.
here is my code in
golang
Screenshot:
Is there any step that I am missing ? Thank you