Email is the way in: hello@nxtolerance.com.

What earns a fast reply

A next-run time that’s wrong. If the calculator lists a run your crontab wouldn’t fire — or misses one it would — send the expression, what the tool predicted, and what actually happened (or should have). Please say which daemon you verified against — cronie, Vixie, Quartz, GitHub Actions, Kubernetes — because “correct” legitimately differs between dialects, and a Quartz schedule pasted into a cron calculator is a known source of confusion on both sides. The dom/dow article and field reference document the divergences we already know about.

A parse error that misidentifies the problem. If the error points at the wrong field or character, quote the expression and the message.

Reasonable feature requests

Things we’ve already weighed: L/W/# support under an explicit “Quartz mode” toggle, a second timezone column next to browser-local times, a crontab -l bulk paste mode, ICU-style descriptions for non-English locales. If you keep reaching for something the tool doesn’t do, describe the schedule you were trying to express — the use case helps more than a feature name.

Corrections to the guides. If something in cron fields, the dom/dow trap, debugging cron or systemd timers is wrong or stale for your platform, quote the line and the correct behavior — and include the page URL.

Response time

Small team, human inbox. Reports with a reproduction case (“0 0 31 2 * should never fire; you showed March 31”) usually get answered within a few days; general feedback may take longer. No tickets, no autoresponder — a person reads it.