How to Schedule Recurring Workflows

Recurring jobs depend on someone remembering to do them

Weekly reminders, month-end checks and daily summaries live in personal calendars, so they stop when someone is on leave.

Event triggers only fire when something changes; nothing happens on a quiet Monday unless a person starts it.

Scripts scheduled on a server ignore the company time zone and can run twice after a restart.

Why this happens

• Building a recurring job on an event trigger and hoping the event happens often enough.
• Not checking Next runs, so a schedule runs at the wrong hour or on the wrong day.
• Forgetting the Stop after date on a temporary schedule.
• Leaving the workflow saved but never activated by an Automation Manager.

Biznsbook addresses this through On a schedule trigger, next runs preview, Run now, company time zone when Business Automation is licensed — start delays, schedule triggers and approval steps run in the background and every run is logged.

Teams lose hours each week to follow-ups, reminders and approvals that live in inboxes and spreadsheets. Making Biznsbook Automation the one place where these rules run — with roles deciding who can switch them on and run history showing what happened — stops silent gaps and duplicate messages.

Step-by-step: Schedule Recurring Workflows

Built for operations leads timing Biznsbook Automation workflows — start delays with cancel-on-event, recurring schedules, and approval steps with time limits.

1. Open the Visual Builder. Go to Automation → Visual Builder. You need the Automation Manager or Automation Builder role.
2. Add the On a schedule trigger. On the Triggers tab, drag the On a schedule tile onto the canvas and select it to open the settings panel.
3. Choose how often it repeats. Set Repeat to Hourly (every 1, 2, 3, 4, 6, 8 or 12 hours), Daily, Weekly or Monthly.
4. Set the time and days. Pick the Time in your company time zone. For Weekly, tick the days under On these days; for Monthly, choose a Day of the month from 1 to 28 or Last day.
5. Add a stop date if needed. Use Stop after (optional) for a schedule that should end, such as a seasonal reminder. Leave it empty to keep running.
6. Check Next runs. The panel lists the next three run times. If they are wrong, fix the time or days before you save.
7. Add steps, save and activate. From the Steps tab, add the actions — for example send email or create task — using merge fields such as {{ScheduledFor}}. Save, then an Automation Manager activates the workflow. Builders use Save & request activation.

Review results after the first full weekly cycle. Adjust roles, mappings, or approvals where the same exception repeats.

Screen-level flows live in the Help Center. This guide focuses on the business process; help articles cover click-by-click navigation.

Common mistakes to avoid

• Mistake 1: Building a recurring job on an event trigger and hoping the event happens often enough. Repeating this each month usually shows up first in missed runs, late escalations or unanswered approvals.
• Mistake 2: Not checking Next runs, so a schedule runs at the wrong hour or on the wrong day. Repeating this each month usually shows up first in missed runs, late escalations or unanswered approvals.
• Mistake 3: Forgetting the Stop after date on a temporary schedule. Repeating this each month usually shows up first in missed runs, late escalations or unanswered approvals.
• Mistake 4: Leaving the workflow saved but never activated by an Automation Manager. Repeating this each month usually shows up first in missed runs, late escalations or unanswered approvals.

Note each recurring failure on the Runs page in your weekly review; each should map to a step in this guide.

Best practices that hold up as you scale

• Open the Visual Builder — Go to Automation → Visual Builder.
• Add the On a schedule trigger — On the Triggers tab, drag the On a schedule tile onto the canvas and select it to open the settings panel.
• Choose how often it repeats — Set Repeat to Hourly (every 1, 2, 3, 4, 6, 8 or 12 hours), Daily, Weekly or Monthly.
• Set the time and days — Pick the Time in your company time zone.
• Add a stop date if needed — Use Stop after (optional) for a schedule that should end, such as a seasonal reminder.

Teams that pair every start delay with a cancel event, preview the next runs of every schedule, and give every approval a time limit avoid orphan escalations.

How Biznsbook supports this workflow

On a schedule trigger is part of Biznsbook Business Automation. Workflows are built on a visual canvas, tested with a dry run that follows IF branches, activated by an Automation Manager, and every run keeps each step's input and output.

next runs preview is part of Biznsbook Business Automation. Workflows are built on a visual canvas, tested with a dry run that follows IF branches, activated by an Automation Manager, and every run keeps each step's input and output.

Run now is part of Biznsbook Business Automation. Workflows are built on a visual canvas, tested with a dry run that follows IF branches, activated by an Automation Manager, and every run keeps each step's input and output.

company time zone is part of Biznsbook Business Automation. Workflows are built on a visual canvas, tested with a dry run that follows IF branches, activated by an Automation Manager, and every run keeps each step's input and output.

Only an Automation Manager activates a workflow; Builders use Save & request activation, Operators can run, pause, resume and retry, and approvers need no Automation role.

Suggested implementation timeline

1. Week 1: List the follow-ups and approvals you repeat by hand and build a first draft with On a schedule trigger.
2. Week 2: Test the draft with sample data, check the highlighted path, and have an Automation Manager activate it.
3. Week 3: Review the Runs page daily, retry failed runs, and tighten conditions that fire too often.
4. Week 4: Add branches, approvals or schedules where the first workflow proved its value.
5. Ongoing: Weekly review using schedules and events together and the Runs page.

Related guides and module pages

Guides: event-driven workflows, recurring workflows, approval steps, delayed triggers.

Modules: Business Automation, CRM guides hub, scheduling guides.

Picking the right repeat

Hourly runs every 1, 2, 3, 4, 6, 8 or 12 hours and suits checks that must happen through the day. Daily runs once at the time you set. Weekly runs on the days you tick, and Monthly runs on a chosen day from 1 to 28 or on the last day.

Days 29 to 31 are not offered so a monthly schedule never skips a short month. Use Last day for month-end work.

How a scheduled run starts

Schedules are checked about every five minutes, so a run starts within a few minutes of its time. Each time slot runs at most once, even if the scheduler is briefly unavailable, so a restart never sends the same reminder twice.

The merge fields {{ScheduledFor}} and {{WorkflowName}} let messages say which slot the run belongs to, which helps when people reply to a weekly email.

Run now and Run on this record

A scheduled workflow can still be started by hand: an Automation Operator or Manager can click Run now on the workflow list or in the builder. Workflows on the Run manually trigger have only that button.

Record pages show an Automation panel with Run on this record for workflows that apply to that record, so a person can rerun a follow-up without waiting for the next slot.

Who can change a schedule

Automation Builders can draft and test a schedule but cannot activate it; Save & request activation emails the managers. Operators can pause and resume an approved workflow without editing it, which is useful over holidays.

Pausing instead of deleting keeps the schedule and its run history, so resuming in the new year needs no rebuild.

Metrics to track monthly

• Delayed workflows that also set a cancel event
• Failed runs retried within one working day
• Scheduled workflows whose next runs match the plan
• Approval requests answered before the time limit
• Documented cancel, schedule and timeout tests in the go-live checklist

Start with three metrics; trend direction matters more than a single point-in-time snapshot.

Manual follow-ups vs Biznsbook Automation

Compare running this by hand with Biznsbook On a schedule trigger and related capabilities.

Schedules and events together

Use a schedule when the timetable matters and an event trigger when the change matters. If a workflow needs both, build two workflows — one on a schedule and one on the event — so each is easy to test. Check Next runs every time you change the time or days, and again after the company time zone changes.

Write this into your automation runbook and revisit it when you add workflows, roles or modules.

Frequently asked questions

How this differs by industry