Scheduler & reminders

Recommended cron

*/10 * * * * cd /path/to/redmine && bundle exec rake redmine_ux_toolkit:run RAILS_ENV=production

The runner records start, finish, status, message, and lock metadata. A stale-lock timeout prevents permanent blocking after a failed process.

Install and verify the central runner

1. Replace /path/to/redmine with the absolute Redmine root and install the cron entry for the same operating-system account that runs Redmine maintenance commands.
2. Run the command once manually from the Redmine root and check its exit result.
3. Open Configure → Scheduler and confirm that last start, last finish, and status were updated.
4. Use Run scheduled tasks now only for verification or an intentional immediate run. Database locking prevents it from overlapping an active cron execution.
5. After installation, wait for at least one scheduled interval and confirm a new successful timestamp.

Interpreting scheduler status

• A recent successful finish confirms that the entrypoint ran; it does not mean every optional job was enabled or due.
• A running lock blocks concurrent executions. An abandoned lock becomes eligible for stale-lock recovery.
• Use the individual job status and message to diagnose reminders, repository refresh, recurring tickets, Helpdesk retrieval, or attachment cleanup.

Ticket reminders

Schedule Redmine's built-in reminder email by time, weekday, due window, and timezone. A daily guard prevents duplicate configured-day sends.

1. Enable scheduled reminders, select the timezone first, then choose send time, weekdays, and days before due.
2. Apply the settings and verify the summarized schedule shown on the Scheduler page.
3. Use the manual send action only when an immediate reminder run is intended; it uses the configured due window and the same lock.
4. Check Redmine's outbound mail configuration if the job succeeds but users do not receive messages.

Monitoring and Helpdesk

Optional monitoring sends one retryable alert per stale or failed incident. When redmine_contacts_helpdesk is installed, non-overlapping mail retrieval can run at a selected interval.

Cron monitoring

Choose a missed-execution threshold and provide a notification address, or verify the displayed fallback from Redmine's notification sender. Normal HTML requests perform a throttled health check, so monitoring also requires users or monitoring software to request Redmine pages. One alert is sent per incident; failed delivery remains retryable, and a healthy central run clears the incident.

Optional Helpdesk retrieval

The controls appear only when redmine_contacts_helpdesk is installed. Select an interval and verify the last successful heartbeat. UX Toolkit launches Helpdesk's established receive task with a fixed command, prevents overlap, and keeps the last successful time when a later attempt fails.