06-scheduled-tasks

Updated on April 21, 2026

Scheduled Tasks is Bizuno’s cron-like scheduler — recurring jobs that run on their own. Nightly backups, monthly statement runs, weekly cash flow reports, training-expiration reminders, auto-emailing of open-invoice lists. Set once, forget, review.

the Scheduled Tasks list showing jobs with next-run times.
the Scheduled Tasks list showing jobs with next-run times.

How to get there #

Menu: Tools → Scheduled Tasks
Direct URL pattern: https://yourdomain.com/?bizRt=bizuno/tools/scheduler

What you can schedule #

  • Database backup — full, nightly, offsite.
  • Statement run — monthly customer statements emailed automatically.
  • Payment reminders — auto-email overdue invoices at 7 / 30 / 60 day thresholds.
  • PO reminders — email yourself open POs past their promise date.
  • Report email — any PhreeForm report emailed on a schedule (P&L on the 5th, cash flow on Mondays).
  • Training expiration reminders — employees & managers notified 60 / 30 / 0 days before expiration.
  • Inventory reorder — generate reorder suggestions nightly.
  • Data cleanup — purge temp files, rotate logs.

Creating a scheduled task #

  1. Click New Task.
  2. Pick a Task Type from the dropdown (backup, statement run, report email, etc.).
  3. Name the task (“Nightly backup”, “Weekly cash flow to owner”).
  4. Configure the task-specific parameters (which report, which recipients, what filters).
  5. Set the Schedule:
    • Frequency: Hourly / Daily / Weekly / Monthly / Custom (cron).
    • Time of day for daily+ schedules.
    • Day of week for weekly, day of month for monthly.
  6. Set the Recipient email(s) if the task emails output.
  7. Toggle Active.
  8. Save.

The scheduled task list #

ColumnMeaning
NameYour label for the task.
TypeBackup, Report Email, Statement Run, etc.
ScheduleSummary of the cron pattern (e.g., “Every day at 2:00 AM”).
Last RunTimestamp and success/failure.
Next RunWhen it fires again.
ActiveEnabled flag.

Run now #

Every task has a Run Now button — fires the task immediately, independent of the schedule. Use it to test after creating a task and to catch up after a missed run.

Run history & logs #

Each task keeps a log of every run: start time, end time, status, output size, and any error. Click a run to see details. A failing task that nobody reads the log of is just silent failure.Important: Scheduled tasks only run if your server’s cron (or equivalent) is configured to poke Bizuno. If a task says “Next Run: yesterday at 2:00 AM” and never fired, your host’s cron is misconfigured. Talk to your hosting provider or admin before adding more tasks.

Starter scheduled task set for Ridgeline #

  • Nightly full backup, 2:00 AM, push to offsite storage, retain 14 days.
  • Monthly statement run, 1st of each month, 8:00 AM, to all customers with open balance.
  • Weekly cash flow snapshot, Mondays 7:00 AM, to owner.
  • Overdue invoice reminders, every day 9:00 AM, at 7 / 30 / 60 day thresholds.
  • Open PO past-promise report, every Monday 8:00 AM, to purchasing (owner).
  • Training expiration digest, Mondays 7:00 AM, to manager and owner.

Editing, disabling, deleting #

  • Edit — change parameters, schedule, recipients at any time.
  • Disable — toggle off without deleting. Good for holiday blackouts or when debugging.
  • Delete — remove the task. Prior run logs are kept for the retention window.

Cron expressions (advanced) #

Custom frequency accepts a cron expression like 0 2 * * * (every day at 2 AM). Reserve for cases the preset schedules can’t handle. Many people get cron expressions wrong; use a cron-expression validator or rely on the presets unless you need the precision.

Tips for Ridgeline Cycles #

  • After creating a new task, hit Run Now to verify it actually does what you expect. The first scheduled run is no time to discover a bad filter.
  • Check the Scheduled Tasks list monthly — any task in red (last run failed) is a silent problem.
  • Be careful with emailed reports to customers (statements, reminders). One bad schedule sent to 300 customers at 3 AM creates 300 support threads.
  • Don’t stack heavy tasks back-to-back at 2 AM. Space them — backup at 2, statements at 3, reports at 4.

Where to go next #

  • Export & Backup — the manual version of the automated backup.
  • Email Templates — wording of the emails generated by scheduled tasks.
  • PhreeForm — build a custom report to email on a schedule.
What are your feelings