Question 1

How do I schedule a job to run every day at a specific time with gron?

Accepted Answer

Import gron/xtime and use gron.Every(1 * xtime.Day).At('HH:MM'), such as daily.At('12:30') from the README example. This sets the job to run daily at that local time.

Question 2

Gron vs robfig/cron: which should I use for Go cron jobs?

Accepted Answer

Gron is better for simple, periodic tasks with its clean API and thread safety, while robfig/cron supports full cron expressions and has a larger community, making it more suitable for complex scheduling needs.

Question 3

Can I add jobs dynamically while gron is running?

Accepted Answer

Yes, you can use c.Add() or c.AddFunc() on a running Gron instance without stopping it, as demonstrated in the full example where jobs are added after c.Start().

Question 4

How does gron handle time zones for scheduling?

Accepted Answer

Gron uses the machine's local time zone from Go's time package, so all schedules are based on system local time. The README notes this in the 'Schedule Parameters' section, with no built-in time zone conversion.

Question 5

Is there a way to make gron jobs persistent across application restarts?

Accepted Answer

No, gron lacks built-in persistence; jobs are in-memory only. You need to implement external storage and re-schedule jobs manually on startup, which adds overhead for recovery scenarios.

Question 6

How to implement a custom job that only runs on weekdays in gron?

Accepted Answer

Gron's schedule doesn't support weekday filters directly. You must extend the Schedule interface with custom logic in Next() or add checks within the job's Run() method to skip weekends, increasing complexity.

gron

What is gron?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions