Skip to content
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

Deploy cron bug #22041

Closed
Luchooo opened this issue Jan 12, 2024 · 3 comments · Fixed by #22042
Closed

Deploy cron bug #22041

Luchooo opened this issue Jan 12, 2024 · 3 comments · Fixed by #22042
Assignees

Comments

@Luchooo
Copy link

Luchooo commented Jan 12, 2024

Version: Deno 1.39.2

When the cron is configured to run every 10 minutes (minute: {every: 10}), and I make another commit to my main branch, triggering a deployment with a cron set to run every 2 hours (hour: {every: 2}), the cron starts running every 2 minutes instead.

WorkAround:

  1. Create a commit to remove cron and push main.
  2. Create a commit to add cron and push main.
@marvinhagemeister marvinhagemeister transferred this issue from denoland/deno Jan 12, 2024
@igorzi
Copy link

igorzi commented Jan 12, 2024

Currently { hour: {every: 2} } means "Every 2 hours, run the job every minute for that hour". If you want the job to run once every hour, you should change it to: { minute: 0, hour: {every: 2} }

@Luchooo
Copy link
Author

Luchooo commented Jan 20, 2024

Currently { hour: {every: 2} } means "Every 2 hours, run the job every minute for that hour". If you want the job to run once every hour, you should change it to: { minute: 0, hour: {every: 2} }

It's working, but I feel that the { minute: 0, hour: {every: 2} } object is confusing. Thank you very much. 👍

@Luchooo Luchooo closed this as completed Jan 20, 2024
@igorzi igorzi transferred this issue from denoland/deploy_feedback Jan 23, 2024
@igorzi igorzi reopened this Jan 23, 2024
@igorzi
Copy link

igorzi commented Jan 23, 2024

Reopening this issue in https://github.com/denoland/deno repo.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants