Calendar schedules belong to the existing Flow engine. Use them for daily work, a chosen weekday, or a day of the month—including the last calendar day. Combine them with date calculations, record actions, document steps, and approvals in the same visual workflow.

Set the calendar precisely#

  • Open Workflows and create a Flow or edit a draft. Select Start and choose a calendar schedule.
  • Choose daily, a weekday, or a monthly day. For month-end, select Last day.
  • Set the local time and IANA time zone. Review the zone shown beside the schedule.
  • Save and validate the draft. Publishing creates the version and activates its trigger; review timing before publishing. Pause stops future automatic starts, and republishing activates a paused Flow.

Last day follows February and leap years. A numbered monthly day beyond a short month uses that month’s last day. At a daylight-saving change, a repeated time uses its first occurrence; a missing time moves forward by the clock change.

Example: one monthly invoice, one line#

  • Find records: select the actual customer and the particular product to use. Pin the product identity if later catalog additions should not change the invoice.
  • Condition: require exactly one eligible item. Stop for correction when it is missing or archived.
  • Date: use the run date in the chosen zone as the issue date. Add a second Date step that adds 30 calendar days for the due date.
  • Create record: make the Draft invoice, linking the selected customer and calculated dates.
  • Create record: make one invoice line linked to the newly created invoice, using the selected item’s current details.
  • Document: choose a compatible template or the invoice’s Document column. Reserve document number if the document should receive a number while remaining Draft.
  • Update record: copy the returned number into an editable Name if desired. If the sheet has an Auto-number field, use that saved reference and select it as the template’s Number source.

Choose execution date or scheduled date#

Date steps use the run’s creation time in the selected zone, or a date bound from an earlier step. Add or subtract calendar days. Use trigger.scheduledAt when the accounting date should be the scheduled occurrence rather than the day the delayed run starts. Once a Date step completes, its result stays stable on retry.

Let AI draft the graph, then check the details#

Ask Ralti can propose the same typed graph using real fields and record IDs. Review the customer, product, selected time zone, month-end setting, due-date calculation, and Draft outcome. The AI-created Flow stays unpublished and disabled until you explicitly publish it. Publishing activates its configured trigger.

Understand missed runs and retries#

A calendar occurrence runs once per local day, week, or month for that Flow, even if its published version changes during the period. A late worker can start a missed occurrence within six hours. Older periods are not backfilled, and a newly published Flow does not create occurrences from before publication.

Record actions and checkpoints commit together. Retrying a failed step in the same run preserves completed invoice and line creation. Starting a new manual run is a separate execution and may intentionally create new work. Inspect the existing run before starting another one. External actions with uncertain outcomes require reconciliation, not blind retry.

Published versions are preserved. Restore an older graph into a draft to review it; this does not republish it or rewrite runs already in progress.